They did the same for me: I was - like the author - vague here, instead of "10/10 perfect score" and thus rejected pretty soon without any further information.
This is one of the long time running instances shutting down, linking to the primary nitter author saying it's the end for all instances eventually. And providing insights from the status page.
If they don't get new guest accounts, they're all going to shut down withing 30 days. It's just left over accounts and caches giving you the impression everything is fine.
Don't forget the rolling DoS herds of scrapers having no more ways to do stuff on their own, which are now trying to use the remaining instances - killing even more.
yeah no, the people complaining about their deleted data clearly wanted to keep using it - so much so, they didn't expect anything close to migrating away to another location
I still have open issues on github for keycloak. One of them is for example, that you can use whitespaces for names, where keycloak can't actually accept whitespaces. So you find that out after you set the global name..
The upgrade path for keycloak is also similarly broken in my experience. Especially the total change in one of the recent versions broke a lot of things, which they are still fixing.
Add no visible LTS or security patching on top, and you end up with something, that isn't usable for any enterprise rollout.
We germans publicly joke about the fact that visiting the older part of your family in those "nice small villages" is always one hell of a culture shock, to put it friendly. Which starts with not saying anything about what they have for political opinions and questions regarding your choice of clothes, sexuality and job.
They probably even have their own town slang. Not any "high german". This is 100% comparable to the political landscape that you have in America (city vs farms outside).
I'm just guessing, but KPXC could emulate a USB device, or - if such things exist - register itself as a security key provider with the operating system
because using a yubikey instead isn't that much more in terms of key-to-browser pipeline - the browser just requests the key from a providing entity