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™

Done both, but I’ve found I rather enjoy the mix of stick and trackpad, emulated as KB+M

I might be slightly biased, but I can also recommend OpenMW for Deck.

I assume both the $20 and $25 prices were during alpha/early access. Was thinking entirely of release pricing.

It’s reasonably easy to guess exactly what you paid for the game, since the only change in price since launch was a $5 bump in January last year. It’s never been on sale.

It releases while I’m on the way back home from a trip to Manchester, might have to bring my Deck so I can play on the flight/train.

Seems to work with my personal setup at least, with two libraries - the default on ~/.local/share/steam, and one on /mnt/storage/steam - and Stardew Valley installed in the secondary storage library

Factorio is great, I’m also a fan of X4.

It’s somewhat amusing how Itanium managed to completely miss the mark, and just how short its heyday was.

It’s also somewhat amusing that I’m still today helping host a pair of HPE Itanium blades - and two two-node DEC Alpha servers - for OpenVMS development.

Going to be really amazing to play Factorio again without knowing how to solve everything.

In general, browser benchmarks seem to often favor Firefox in terms of startup and first interaction timings, and often favor Chrome when it comes to crunching large amounts of data through JavaScript.
I.e. for pages which use small amounts of JavaScript, but call into it quickly after loading, Firefox tends to come out on top. But for pages which load lots of JavaScript and then run it constantly, Chrome tends to come out on top.

We’re usually talking milliseconds-level of difference here though. So if you’re using a mobile browser or a low-power laptop, then the difference is often not measurable at all, unless the page is specifically optimized for one or the other.

There’s a bunch of extensions that allow you to switch user-agent easily, I personally use this one, it includes a list of known strings to choose between as well.

They used to also use the unreleased version 0 of shadow DOM for building the Polymer UI, which - being a Chrome-only prototype - understandably didn’t work on Firefox, and therefore instead used a really slow Javascript polyfill to render its UI.

I haven’t checked on it lately, but I imagine they must’ve changed at least that by now.

One thing you can test is to apply a Chrome user-agent on Firefox when visiting YouTube. In my personal experience that actually noticeably improves the situation.

Go has a heavy focus on simplicity and ease-of-use by hiding away complexity through abstractions, something that makes it an excellent language for getting to the minimum-viable-product point. Which I definitely applaud it for, it can be a true joy to code an initial implementation in it.

The issue with hiding complexity like such is when you reach the limit of the provided abstractions, something that will inevitably happen when your project reaches a certain size. For many languages (like C/C++, Ruby, Python, etc) there’s an option to - at that point - skip the abstractions and instead code directly against the underlying layers, but Go doesn’t actually have that option.
One result of this is that many enterprise-sized Go projects have had to - in pure desperation - hire the people who designed Go in the first place, just to get the necessary expertice to be able to continue development.

Here’s one example in the form of a blog - with some examples of where hidden complexity can cause issues in the longer term; https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride