I made an NFC/QR code card for my wifi details at home, and that also includes the details written in clear text on the card, since some devices simply don’t do QR (or NFC in my case).

Someone pulled some DRAM cost graphs, and with the >500% increase that’s happened, the Deck did have to rise at least $200 to remain viable.

We really can’t have nice things, first crypto and now AI insanity is really doing its best to remove computing as an affordable hobby.

It doesn’t really solve my use-case, since we do a combination of direct stream when possible, as well as local sync/cache but only for transcoding purposes. As well as local users only, with the federated sharing taking care of permissions, so that we don’t transfer user information between eachother.

Jellyswarrm is certainly a lot closer than other solutions people have suggested though.

The lack of library sharing is what’s keeping me on Plex.

The ability to watch media across servers, and even transparently pull it for local transcode when necessary is just an amazing feature.

Jag har läst nog mycket AI-genererad kod för att inte våga lita på programvaror där AI är en huvudförfattare. Om någon har kopierat ihop koden för hand så har de iallafall gjort aktiva val runt kodstyckena som valts ut, och så finns det någon form av domänkunskap i hur alla kodstyckena är hopkopplade i den slutgiltiga programvaran också.

Med genererad kod finns det varken någon sådan domänkunskap, och inte heller någon kvalitékontroll på kodstyckena som använts för att skapa slutresultatet.

Sen så är ju AI-generering inte direkt kompatibelt med foss heller, varken licensmässigt eller som ren gemenskapsfråga.

Bara lite synd att Fedibook är byggt med AI.

Added an edit with the filter line

I actually recently added the Microsoft logout page to µblocks domain filter at work, since it would every now and then trigger a logout the very first page load after I’d log in to the email there.

This has also somehow caused a bunch of other AD-connected systems to suddenly behave a lot better when it comes to session termination.

Edit: Since people were asking for it, this is what you need to add to the “My filters” tab in your UBO config;

||login.microsoftonline.com/common/oauth2/v2.0/logout^$document

This will prevent any requests from redirecting you to log out, timeouts etc will still invalidate your session.

No longer an assumption - from itch themselves: https://itch.io/updates/update-on-nsfw-content

Assuming that this is due to pressure from VISA/MasterCard - like it’s been with Steam.

It’s patently bizarre how a company whose only purpose is transferring money from account A to B can then arbitrarily decide what people are allowed to buy and sell.
It’s one thing to refuse to be an acceptable payment method for NSFW games, but to forbid the store from selling them at all? That’s just megalomania, and a great pointer to why monopolies (and duopolies) are A Bad Thing™

I guess they’re going to complain about the fact that Kobo e-readers use regular microSD cards for onboard storage next, instead of soldering the chips directly to the board.

For sparkling, it’s commonly referred to as “homeopathic lager” among colleagues - i.e. without any active ingredients.

Interesting, that’s definitely not what I’m seeing from regular use. Are you running any added applications? LDAP? SSO? External mounts?

Are you looking at data rates or IO operations? Because this is almost exclusively stat queries, i.e. inode queries.

Oh yeah, CPU usage is basically zero, and memory usage of the PHP code itself is also basically nil compared to other software I run. It’s just the sudden storms of IO requests that causes issues, and since those come over a network pipe it causes issues for other pieces of software as well.

Again, it works until it requires reloading, i.e. the next update of any component or the next restart of the server.

I’m also running an inode cache on the client side, on top of the persistent opcache, but due to the sheer number of files that Nextcloud consists of it still generates a frankly ridiculous amount of calls when it needs to invalidate the cache. If you’re running on local drives then that’s likely much less of an issue, regardless of what kind of drive it is, but this is hosted on machines that do not have any local storage.

Yep, those values are actually somewhat tame compared to my own cache tuning, the issue remains that the code requires reloading PHP files from disk during runtime in order to support applications and updates, which - even if it doesn’t happen often - causes IO storms that temporarily break both Nextcloud as well as other software.

Currently working to move away from Nextcloud myself, it’s PHP nature causes IO storms when it tries to check if it needs to reload any code for incoming requests.

All OpenWRT-based routers have the option of built-in DNS-based adblock, can thoroughly recommend the Turris routers for such things.

It’s worth noting that the ESS suite Chart is absolutely not built to be community-viable, it’s built for the kind of single-purpose deployments that Element offer hosting for, and it also breaks almost all Kubernetes best practices. Which is actually not wrong per-se. Element need to be able to maintain it after all, and since they don’t have the Kubernetes know-how to build generic components, it makes sense to instead bundle a fully integrated solution which they are comfortable with developing and debugging.

They’re definitely slowly but steadily rewriting Synapse in Rust as well, that’s been an open and ongoing project for a while now. You can see that just by looking in the Rust folder in the Synapse sources.
I strongly doubt that they have the “rest” of the application rewritten internally and keeping it hostage for paid hosting though, it’d cost them too much to keep separate codebases for such a thing.

The “Synapse Pro” offering is most likely just the regular Python+Rust Synapse, but with a few additional HA components and some workers written in Rust for efficiency, just like how there’s community workers written in both C# and Go for performance reasons.