it’s opt-in, per app. Meaning unless old apps are patched and recompiled, they will be inaccessible.

it means that you have to manually reposition every single window, every single time. for any and all apps, by design

followed by “worcestershire sauce”

you mean it doesn’t work when the device is turned off? weird! /s

by issues I mean breaking existing users’ workflow, possibly literally locking them out (I personally use a yubikey with my keepass db, for example).

There is a very simple solution he could have done: not rename the existing package. Just give his fork a new name. That’s it, everybody is happy.

So yes, he is the one causing issues. Because the issue isn’t in the features he removed, but by breaking the users’expectation that the package they installed yesterday, is the same one they’re updating today.

well it is that one person causing issues

when in need, cry out for mommy!

there is the keepassxc-cli command. And it also supports ssh keys with integration with ssh-agent. So yeah

one of the extensions has the description: “an easy flow to update passwords”

If that has to be an extension, then this sucks

markdown is standardized? I haven’t found two parsers that parse the same file the same for any but the most trivial documents

nah man, gotta be more specific. When those stuff work on every application.

A screen reader protocol for blind people that requires the app to be recompiled and opt-in to being accessible to accessibility tools, is not a replacement for one that worked for every application. Old apps will become impossible to use for some people with accessibility issues. Though wayland fanboys would tell you to shut up and be happy that a protocol exists, while failing to acknowledge that the protocol is literally fucking useless by design.