And it’s not even just the people traveling here from the future trying to do it, it’s also travelers from the past.

More expensive than the base-level Xbox/PS controller, but cheaper than their pro-version - as well as the Joy-Con 2s.

I’m down for it, nobody else is doing trackpad controllers after all.

I’m really happy to see a piece of news about “… your companion for …” and it not being about yet another soulless LLM chatbot.

What I’m hearing here is that they really need to build a flatpak, so there’s a sane install method for it.

Considering this is anubis, the project created explicitly to block AI crawlers?

I absolutely love that zip-tie mounting solution, it’s the kind of thing I wish I saw in more homelab setups.

People joke about linux.exe, but there was such a thing as andLinux/coLinux

I really do hope that Funkwhale get their 2.0 release out soon, should make self-hosted Spotify-like stacks simpler to do, and the fact that it works for creation and distribution as well is great.

I think the login-redirect system is just broken for ADFS, it feels like it adds all the SSO-logout URLs for all systems you’re logged into to the redirect queue when it times your session out.
Which means you’ll have to log in enough times to exhaust that queue before it finally reaches the actual system you’re trying to log into.

But that’s just an assumption.

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™

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.