radikal.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
radikal.social was created by a group of activists to offer federated social media for the radical left in and around Denmark.

Administered by:

Server stats:

159
active users

#update

14 posts9 participants0 posts today

So, I am stuck trying to apply the current #Mastodon update. Note that there may be many good reasons why, chief among them, that I am self-taught and very much in the "trying stuff out half-blindly while learning"-stage. Thankfully, nothing broke irreversably just yet.

If anyone here feels like helping a noob out, or just loves a conundrum, details can be found here:

lemmy.abnormalbeings.space/pos

lemmy.abnormalbeings.space[SUPPORT][Mastodon] Getting stuck on trying to apply the latest update - AbnormalLemmingscross-posted from: https://lemmy.abnormalbeings.space/post/804932 [https://lemmy.abnormalbeings.space/post/804932] I have searched around for answers to this, but so far, the solutions I found and tried have not been working for me. Thankfully, the update isn’t that critical, so time is not of the essence as of now. But I fear, the problem will only persist. So, bit of a headscratcher: I am following the guide to upgrade (no Docker) from here. [https://github.com/mastodon/mastodon/releases/tag/v4.3.7] Simple enough, right? Sadly, I keep getting: ~/live$ RAILS_ENV=production bundle exec rails assets:precompile I, [2025-04-03T20:30:30.072648 #981372] INFO -- : [dotenv] Loaded .env.production Mastodon and Webpacker requires Yarn ">=4 <5" and you are using 1.22.22 Exiting! So, the proposed solution? Using corepack as intended. That, at first, upon entering “corpack prepare” and “corepack enable” in succession, seemed to run silently and without errors/warnings. But it changed nothing at all for the error message. Prompting me to search around, haphazardly try to apply fixes, trying to remove and reinstall yarn, “the usual”. My last attempt was to globally remove yarn and corepack with npm and then re-install both. Since then, a new, exciting error is happening: ~/live$ corepack enable Internal Error: EACCES: permission denied, symlink '../lib/node_modules/corepack/dist/pnpm.js' -'/usr/bin/pnpm' at async Object.symlink (node:internal/fs/promises:1005:10) at async EnableCommand.generatePosixLink (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23156:5) at async Promise.all (index 0) at async EnableCommand.execute (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23143:5) at async EnableCommand.validateAndExecute (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:20258:22) at async _Cli.run (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21195:18) at async Object.runMain (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23642:19) Oh, and when trying to install yarn and corepack, now, I get: ~/live$ npm install yarn npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch npm error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log ~/live$ npm install corepack npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch npm error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log ::: spoiler the logs in question: $ cat /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.2.0 2 info using node@v22.14.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mastodon/live/.npmrc 5 silly config load:file:/home/mastodon/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm install yarn 8 verbose argv "install" "yarn" 9 verbose logfile logs-max:10 dir:/home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z- 10 verbose logfile /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368 13 silly logfile done cleaning log files 14 silly idealTree buildDeps 15 verbose stack Error: Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 15 verbose stack at unsupportedURLType (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:369:15) 15 verbose stack at fromURL (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:428:13) 15 verbose stack at Function.resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:110:12) 15 verbose stack at #nodeFromEdge (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1039:22) 15 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:904:35) 15 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7) 15 verbose stack at async Promise.all (index 1) 15 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5) 15 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 16 error code EUNSUPPORTEDPROTOCOL 17 error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 18 silly unfinished npm timer reify 1743710053061 19 silly unfinished npm timer reify:loadTrees 1743710053064 20 silly unfinished npm timer idealTree:buildDeps 1743710057205 21 silly unfinished npm timer idealTree:#root 1743710057206 22 verbose cwd /home/mastodon/live 23 verbose os Linux 6.1.0-31-amd64 24 verbose node v22.14.0 25 verbose npm v11.2.0 26 verbose exit 1 27 verbose code 1 28 error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log ~/live$ cat /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.2.0 2 info using node@v22.14.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mastodon/live/.npmrc 5 silly config load:file:/home/mastodon/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm install corepack 8 verbose argv "install" "corepack" 9 verbose logfile logs-max:10 dir:/home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z- 10 verbose logfile /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368 13 silly logfile done cleaning log files 14 silly idealTree buildDeps 15 verbose stack Error: Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 15 verbose stack at unsupportedURLType (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:369:15) 15 verbose stack at fromURL (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:428:13) 15 verbose stack at Function.resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:110:12) 15 verbose stack at #nodeFromEdge (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1039:22) 15 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:904:35) 15 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7) 15 verbose stack at async Promise.all (index 1) 15 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5) 15 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 16 error code EUNSUPPORTEDPROTOCOL 17 error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 18 silly unfinished npm timer reify 1743710065916 19 silly unfinished npm timer reify:loadTrees 1743710065919 20 silly unfinished npm timer idealTree:buildDeps 1743710070343 21 silly unfinished npm timer idealTree:#root 1743710070344 22 verbose cwd /home/mastodon/live 23 verbose os Linux 6.1.0-31-amd64 24 verbose node v22.14.0 25 verbose npm v11.2.0 26 verbose exit 1 27 verbose code 1 28 error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log ::: Thankfully, mastodon is still working, no database issues, nothing indicating I fucked up beyond repair yet. I am a bit at a loss, unfortunately, but eager to use my fuckup as a learning experience - am glad to hear any and all more experienced folk chiming in!
Continued thread

#UPDATE

🇫🇷 The French media group NRJ stated in a comment for Libération that it was “astonished to learn” from The Insider's article about its brand being used in the occupied territories of #Ukraine

NRJ promised to terminate its contract with Gazprom Media and stop broadcasting in occupied Donetsk.

theins.press/en/news/280179

The Insider · French radio brand NRJ to terminate its contract with Gazprom Media and stop broadcasting in occupied Donet...By The Insider

Big update for abnormalbeings.space !

Across #Mastodon, #Lemmy and #PeerTube, as well as a first version of a landing page, also: the first donation happens (thank you very much!) - read all about it on Lemmy:

lemmy.abnormalbeings.space/pos

lemmy.abnormalbeings.space25/03/28: Beginnings of a unified design, new fancy (resource-hungry) landing page, money!!! and more - State of abnormalbeings.space - AbnormalLemmingsSo, a lot of visible things got done today, and I am at a point, where I think an update makes sense. Also, starting now, I will not create annoncement/update posts for every change, but bundle them in “State of the Website”-posts like this. BEGINNINGS OF A UNIFIED DESIGN As you may have noticed, the favicon, icon and banner for the instance have changed, and there are now links to the other two fediverse services in the sidebar: [https://lemmy.abnormalbeings.space/pictrs/image/699c895a-22c7-42b6-8e52-edd7874d3bbb.png] This is part of creating a more unified design for all three services and the website as a whole. You can also follow the links here: [https://lemmy.abnormalbeings.space/pictrs/image/af118d0e-8cd8-4876-a0a1-ed505a5d3e64.png]https://videos.abnormalbeings.space/ [https://lemmy.abnormalbeings.space/pictrs/image/77a09580-7dc7-4189-a9b9-059bbdf8bf23.png]https://lemmy.abnormalbeings.space/ [https://lemmy.abnormalbeings.space/pictrs/image/af427312-13fa-4cb8-9a59-51b5b50f619e.png]https://toots.abnormalbeings.space/ The one service lacking behind is mastodon - I have not yet been able to easily figure out a way to easily put images via Markdown or otherwise into the frontpage - but eventually, I will find a way. If you know how - feel free to answer the question here [https://lemmy.abnormalbeings.space/post/578809], for me and any future people stumbling over Fediverse search results. As a long-term-goal, creating more unified theming with custom CSS along all three services is what I will be aiming for. That, however, is in the “one day, probably, maybe” phase of things at the moment. NEW CUSTOM PEERTUBE LANDING PAGE If you follow the link to the PeerTube instance co-hosted here [https://videos.abnormalbeings.space/home], you will see, that it no longer defaults to putting you into the “Browse Videos” tab - instead, there is now a custom landing page, with trending videos and recommended channels. There is no thought put into the order of channels, so, if your favourite is appearing further down, that is not me valuing it less. Some screenshots how it should look like: [https://lemmy.abnormalbeings.space/pictrs/image/060dbabb-ecbd-4035-8067-03dc7b0a47a8.png] [https://lemmy.abnormalbeings.space/pictrs/image/edfd4dbb-0d91-40d7-9bbb-3f4513e78175.png] NEW OVERALL LANDING PAGE (WARNING: NOT RESOURCE EFFICIENT) So, I am not good at CSS. Not good at HTML either. Really - not good at other programming languages, really, but maybe more adequate there. I had been wondering what best to use for a landing page when people visit abnormalbeings.space [https://abnormalbeings.space/] directly. Then I remembered: One tool I do have some experience with is Godot! So, behold, if you follow the link in the paragraph above, you should get a first version of a huge flashback to resource inefficient old flash sites (but in HTML5 and Godot, instead): [https://lemmy.abnormalbeings.space/pictrs/image/86829631-f6d1-4496-9869-036f78cb8a86.png] As of now, there has been no testing of, or optimization for, mobile clients. Also, the legal disclaimer section is empty, as of this post. Really, the landing page should only be reached if you look for it, or as a link in my games [https://abnormalhumanbeing.itch.io/] (where I will add them later this week, and in any new releases) Some optimizations should follow eventually, but it isn’t the highest priority. MONEY!!! I’m trying not to beg too much and create pity-donations, but one reality of my life is, that I am living on subsistence-level disability payments, paying for this server out of pocket. Mind you, that is subsistence-level in a European country with a not-yet-completely-gutted social system, so I will survive, and the server will stay up indefinitely, and any and all of my services/games will always remain free to access. But any donations are of course always welcome, so I am really happy to announce, that the project got its first one: [https://lemmy.abnormalbeings.space/pictrs/image/63af536b-dc16-48ed-915f-01d0372ee6df.png] Thank you so very much! It is highly appreciated, and will keep me afloat a little more securely! Donations are only possible through Liberapay - I am genuinely not in this for the money, and I don’t want to ever lock features behind donation ranks like on Patreon, also, I am all-in on FOSS and the Fediverse. So other platforms will not be added any time soon. If you want to support me as well, I’d of course be very thankful, just click the link below: [https://liberapay.com/assets/widgets/donate.svg] https://liberapay.com/Wxnzxn/ Anyway, that is that for this update - thank you for reading, thank you for using the Fediverse, and here’s hoping you’ll have a great day!

Managing a large-scale knowledge platform? Traditional CMS often lack flexibility for editorial workflows & multilingual content.

The Historical Dictionary of Switzerland (HLS) turned to XWiki for:
✅ Open-source customization
✅ Granular access control
✅ Seamless collaboration
✅ Future-proof scalability

Looking for an alternative to traditional CMS? Read how HLS modernized its platform: xwiki.com/en/Blog/HLS-open-sou

slrpnk.net/post/19958860

How to install #Windows11 with better #privacy and user control.

There are extremely many people still using Windows 10 or even older, which will become a real security issue soon.

This guide is for people that need to keep using Windows. I used it to upgrade an unsupported Laptop to Windows 11, which is worlds better than Windows 10, after you clean it up. It makes Windows ***almost*** a nice OS ;)

slrpnk.netMaking sure you're not a bot!