I’m honestly baffled. These are two companies that are clearly past their best days, largely because of a string of controversial decisions in recent years that have pushed many users toward alternatives that feel more reasonable and do not attempt to re-educate users’ behavior.

On point 👌

Yup piper is a good option. install:

• extra/speech-dispatcher
• aur/piper-tts-bin
• aur/piper-voices-common
• aur/piper-voices-…-…

Then configure speech-dispatcher according to arch wiki and enjoy TTS via command line spd-say or in firefox directly (switch to reading mode for a website).

It differs between software vendors and versions. For example, if you’re using a recent version of gnupg, your key is most likely stored using openpgp-s2k3-ocb-aes. Use that as a starting point to find more information on how good the protection is. I personally would rate it a fair bit lower compared to the key derivation methods used in keepass which focus more on brute force resistance.

You should not store your privates keys unencrypted. In fact by default your keys are stored password protected just as if you’d store them in keepass.

Poor license choice. If you really want to enforce it, don’t rely on MIT.

There is indeed a big difference between requiring a specific password vs. requiring a specific device or software to be able to use the service. Keep in mind that big tech can very conveniently leverage this technology to lock you in. For example think about Apple, Google and Microsoft requiring you to use passkeys, and then later require you to use your certified phone and app. Most people will not be able to “go elsewhere”.

You seem to be falling for what the author was writing about. Only because you could technically try to use keepassxc to store passkeys, that does not mean that it will work. You see passkeys were build in a way the service you’re trying to login to can decide if they accept your keepassxc for passkey storage or not. It looks like you are in control when you are actually not.