I don’t know much about Proton. Isn’t their back end proprietary though?

That’s actually a good point too: Vaultwarden is fully open source. The official Bitwarden server also has proprietary components.

Not pedantic at all. Google lied about RCS being an open standard.

The pedantic point would be saying that RCS, the protocol, is technically open, but the specific implementation that Google is pushing and being adopted is proprietary 🤓

So yeah. Totally fair point and fuck Google for their RCS bait-and-switch.

Don’t get me wrong: BW is still a pretty good service, and the proprietary code is still readable by anyone, but the fact that they’re moving a bunch of their previously open source licensed code to something that’s source available is definitely unfortunate.

KeePass, on the other hand, has tons of actually open source clients, which definitely gives them an edge for people that don’t mind syncing their own DB.

Their new, native android app is also using more and more of their proprietary SDK. It’s not something they’re trying to fix.

Bitwarden. Most people think that their application is open source, but more and more of their code has shifted from the GPL/AGPL licensed code to code in their SDK, which is under a proprietary license. This led to their new Android app being disqualified from being hosted in F-Droid repos.

Keyguard was supposed to be an open source Bitwarden client, but the dev chose to use a custom proprietary license, so that is source available as well.