keepassxc VS privacytools.io

KeepassXC supports exporting, but i don't think it is released in a stable version / to the public yet:

https://github.com/keepassxreboot/keepassxc/pull/8825

If you use KeePass, make sure you use the KeePassXC variant. KeePass is dead.

https://keepassxc.org/

That's why you use the superior one, KeePassXC, as linked in the NIST link: https://github.com/keepassxreboot/keepassxc/discussions/9433

Over there, they got pissed about people constantly bugging them about it and closed the bug with the last comment reading:

for the internet, use a password manager like keepassxc with a strong password.

Another regression is that KeePassX/C AutoType doesn't work with Wayland, so now instead of a simple CTRL+V in KeePassXC, I have to separately copy and paste the user and the pass.

https://github.com/keepassxreboot/keepassxc/issues/2281

FYI, Privacy Guides is a shitshow. It was formerly privacytools.io[1], and in 2019, the creator[2] of privacytools.io stopped contributing[3] and a new contributor[4] immediately focused on donations[5], became the admin[6] and took control[7] of most assets, including donations but excluding the domain and Twitter account[8]. In 2021, the creator of privacytools.io launched a new privacytools.io[9] and added affiliate links[10], and the Privacy Guides team shut down r/privacytoolsIO rather than return it[11] to the creator. Like I said, a shitshow.

[1] https://github.com/privacytools/privacytools.io

[2] https://www.reddit.com/user/BurungHantu

[3] https://github.com/privacytools/privacytools.io/commits?auth...

[4] https://github.com/jonaharagon

[5] https://github.com/privacytools/privacytools.io/commits?afte...

[6] https://github.com/privacytools/privacytools.io/commit/4b60a...

[7] https://redd.it/tuo7mm

[8] https://twitter.com/privacytoolsIO

[9] https://redd.it/pxtw2y

[10] https://www.reddit.com/r/VPNTorrents/comments/raftz6/i_made_...

[11] https://redd.it/qk7vn0

Yes, we know you're still mad we won't add Threema. It was thoroughly discussed in our old organization.

en 2019: Signal has copious privacy issues making it unfit for privacytools.io endorsement.

Signal is just another walled garden and has a lot of other problems too: https://github.com/privacytools/privacytools.io/issues/779

Or the fork which is much more active these days https://docs.searxng.org/

In the past it Lukol served Google Ads: https://github.com/privacytools/privacytools.io/issues/1557#...

Never heard of it. Fastmail apparently never made it on to the privacytools.io list for its geographical location. See here for some other recommendations. There are also malifence and posteo. I use posteo and mailbox.org. The main two weird things about posteo is that there is no spam folder (detected spam is rejected with no option to change this), and you can't use a custom domain (because they don't want to have any information on you/your name). Mailbox.org can optionally reject spam and lets you use your custom domain. I like it a lot so far.

The correct link is https://github.com/privacytools/privacytools.io/pull/657

Worth noting the "admins" of that site wrote the content for it, check for yourself https://github.com/privacytools/privacytools.io/commits/master BurungHantu hadn't written anything really since 2016.