vrighter

because of ai stuff. For these kinds of things, they are perfectly happy to advertise unprecedented 99% accuracy rates, when in reality, non ai tools are held to much higher standard (mainly that they are expected to work). If the code I wrote had a consistent, perpetual 1% failure rate (even after fixing it, multiple times), I'd have been fired long ago.

99% chance to hit in xcom means you'll accidentaely fill up the bathtub without a single drop hiting the actual toilet.

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!

have you seen the show Severance? This is exactly the premise of that show.

if you don't play certain multiplayer games that use invasive anti-cheat software, then you really should give it a go! It's gotten to the point where I first buy games and then worry about compatibility. The vast majorityic just work with minor tweaks at the most (setting some launch arguments usually)

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

both have 16 gb ram. Older desktop, newer laptop, so cpu performance is roughly equal. Both use an ssd