Opprett kontoLogg inn

Nylige søk

Ingen søk nylig

Alternativer for søk

Ikke tilgjengelig på snabelen.no.
snabelen.no is one of the many independent Mastodon servers you can use to participate in the fediverse.
Ein norsk heimstad for den desentraliserte mikroblogge-plattformen.

Administrert av:

Serverstatistikk:

449
aktive brukere

snabelen.no: OmStatusProfilkatalogPersonvernregler

Mastodon: OmLast ned appenHurtigtasterVis kildekodev4.3.7

#update

32 innlegg23 deltakere0 innlegg i dag
Offentlig *
Aptivi

Samsung Canada reveals One UI 7 release date for S24 and Fold/Flip6

Telus has updated their software update schedule in their official forums to reflect latest information that they have just obtained directly from Samsung Canada. They have warned that “all dates are approximate and subject to change” when releasing schedules aimed at the future.

This piece of information, however, is very interesting as Samsung Canada has confirmed that they’d be releasing the official One UI 7 update to the following devices in April 11th:

  • Galaxy S24 series
  • Galaxy Z Fold6
  • Galaxy Z Flip6

This almost aligns with the official Samsung Newsroom announcement for Canadian users except that there is a one-day delay when it comes to release dates.

Are you excited for One UI 7?

#Android#Android15#AndroidV
Offentlig
Abnormal Human Being

New update for the state of abnormalbeings.space available on Lemmy, check it out if you are interested:

A proper backup plan, Mastodon update + learning experience, PeerTube changes, looking for mods - State of abnormalbeings.space

lemmy.abnormalbeings.space/pos

lemmy.abnormalbeings.space25/04/05 A proper backup plan, Mastodon update + learning experience, PeerTube changes, looking for mods - State of abnormalbeings.space - AbnormalLemmingsSince the last update [https://lemmy.abnormalbeings.space/post/587275], there haven’t been any sweeping changes, but enough for a report, including one that should put people at ease: Yes, you won’t be raw dogging these services no longer, thanks to greater financial security from the donation mentioned in the last update, I was able to start this month’s budgeting by booking a separate storage for: ::: spoiler REGULAR BACKUPS Until now, my backup “plan” was, “I upload a backup image to a local NAS here at home, that has very old second hand HDDs, whenever I manage to remember”. That was… not acceptable, really. I will now have borgbackup running for incremental backups to a separate storage box by Hetzner (in Germany instead of Finland, for one more degree of separation). There will be separate, complete, incremental backups daily/weekly/monthly, starting today. It won’t guarantee data security on the same level as even more professional services, but I think anyone using this instance or others can rest a little more easily. ::: :::spoiler MASTODON UPDATE Another thing people can probably rest a bit more easily about: There was a minor update for mastodon, which I applied to toots.abnormalbeings.space [https://toots.abnormalbeings.space/home], bringing it up to date to version 4.3.7. Beyond just quickly giving a heads-up to report any potential issues, this is noteworthy, because it came with me learning a very important lesson about environment sanitising, that more experienced folks probably though to be self-evident. You can check out my learning journey here if you are interested. [https://lemmy.abnormalbeings.space/post/804932] Having the opportunity to learn about what are best practices - one of the Achilles heels of, I wager, not just me as a self-taught admin - is great, especially if the learning process and answers can add to the fund of knowledge within the Fediverse! ::: ::: spoiler PEERTUBE CHANGES Videos.abnormalbeings.space [https://videos.abnormalbeings.space/home] saw some changes, too. I, sadly, had to change up the registration process to manually confirming users again, as I had several accounts registering - sometimes avoiding bans with throwaway mail addresses - and uploading at best highly suspicious content that I was not able to moderate due to language barrier, or just videos outright against the rules. Additionally, I updated the about info, structured it more, removed redundancy of the rules, clarified moderation policy and added more contaft info. Changes can be viewed here. [https://videos.abnormalbeings.space/about/instance/home] There’s also been some changes to the landing page [https://videos.abnormalbeings.space/home] - now sporting current livestreams, as well as a separate small section for trending local videos: [https://lemmy.abnormalbeings.space/pictrs/image/55afc263-d0ad-4ef2-8af1-3fc71018947f.png] [https://lemmy.abnormalbeings.space/pictrs/image/6cf5231e-c891-4020-936b-dbd357e795a8.png] Alongside this, I will now start to weekly rotate the recommended channels list, rotating the last row into first place, as to make it a fairer system for channels that ended up at the bottom before. There really is little rhyme or reason to the way I sorted them, so this seemed like a good compromise to me. Also, in good news: the amount of accounts on videos.abnormalbeings.space has ballooned up to 30+ (including 3 accounts created by myself). This is some great growth, and I am happy to say, that there has been some legitimate content appearing on there, beyond my silly meme videos and that one trailer for my by now very old game. Thank you all for putting your trust in me, server resources still allow for a lot more users! (This goes even more so for Lemmy and Mastodon, of course). ::: ::: spoiler LOOKING FOR MODS Realising the user growth on particularly PeerTube, I’d also be very interested in people applying as volunteer moderators. You’d have to have a local account on at least the service you want to mod, plus on matrix [https://matrix.to/#/#abnormalbeings:matrix.abnormalbeings.space] for behind-the-scenes discussion. Applications are welcome on matrix, in the Applications channel! [https://matrix.to/#/#applications:matrix.abnormalbeings.space] Bonus points if you speak other languages than English and German, which I have covered! Currently, it would 100% be a volunteer position. Long term, if this project ends up getting more in donations than the server cost, I’d think it would be cool to share any excess with an established mod/admin team - but that sentence right here should be, at this point, treated as “a random thought I am having.” I can neither promise that amount of donations ever happening, nor promise that being possible easily whenever it were to happen. ::: And that is that for the newest state of the server update. Thank you for reading, thank you for using the Fediverse, stay awesome!
#fediverse#lemmy#PeerTube
Offentlig
Aptivi

Making Projects Better

Making our projects better than before is one of our most important things that we have planned to do. We have improved the build system across all projects by introducing the tools repository on GitHub that is used as a submodule. Our strategy for this plan is to make sure that all our projects get the highest quality possible, while aiming for more.

Announcements for new release of our flagship projects will be made every major version or a version that is worth talking about. Not only updates will be done, but projects that are new to the programming industry will be made to allow developers to have more options according to the program.

Recently, we have started improving the documentation of the Terminaux project for the upcoming release. We have currently restructured the cyclic writer documentation so that a single page is split to multiple pages by category. This helps find information more quickly.

In the second half of the year, we are planning to introduce changes to our work plans so that we’d be more open. Confirmed additions, improvements, and other updates will be added to every repository’s GitHub Projects, straight from the internal information. This is to let the users know of the roadmap of all our projects in a more transparent manner.

After the release of the upcoming Nitrocid version series, we’ll make sure that other projects get their own development time as we are striving to improve them with new features and other general improvements. Because the upcoming version of Nitrocid is currently in a stage where it needs to be adjusted for the next Terminaux version, a beta program will be introduced. This is to gain feedback from developers and users, and we listen to all feedback!

Making sure that we fulfill our promises to you, we’ll keep you informed of any new updates regarding our projects. Meanwhile, normal development for all projects will start on April 6th, and we hope that we introduce you to new, exciting features. Are you ready for the most exciting moments?

Image by freepik

#bassboom#C_#csharp
Offentlig
Aptivi

Ubuntu on phones now receive initial VoLTE support

If you are using one of the supported Ubuntu Phone devices, such as a Volla 22 (contains a MediaTek Helio G85 SoC) or a Fairphone 5 (contains a Qualcomm QCM6490 SoC), you can now use VoLTE on your device.

The necessary modifications for both SoC vendors have been added to both the Noble Numbat version and the Focal Fossa version so that VoLTE works on these devices that have Ubuntu Touch installed. However, for other phones, such as Xiaomi and Google Pixel phones, it’s on the developer who created the port to modify it so that it works with VoLTE.

While they have tested the functionality with both high-quality voice calls and SMS messages, they have reported issues when working with MMS. In the status bar, if your phone shows VoLTE, this means that you can have high-quality voice calls.

In order to try out VoLTE support, you must make sure that:

  • your phone is running the latest version of Ubuntu Touch,
  • your phone supports VoLTE, and
  • your carrier and your cellular plan support VoLTE.

Image by freepik

#Fairphone#Fairphone5#news
Offentlig
Abnormal Human Being

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!
#sysadmin#techsupport#update
UtforskTidslinjer
Om