Pull request #10974 introduces the @bitwarden/sdk-internal dependency which is needed to build the desktop client. The dependency contains a licence statement which contains the following clause:

You may not use this SDK to develop applications for use with software other than Bitwarden (including non-compatible implementations of Bitwarden) or to develop another SDK.

This violates freedom 0.

It is not possible to build desktop-v2024.10.0 (or, likely, current master) without removing this dependency.

you are viewing a single comment's thread
view the rest of the comments

[–] unrushed233@lemmings.world 17 points 2 months ago (1 children)

Bitwarden can't be compared to KeePassXC. Bitwarden is fundamentally built around a sync server, whereas KeePass is meant to exclusively operate locally. These are two very different fundamental concepts for, you know, how to actually store and access your passwords.

[–] Hexarei@programming.dev -1 points 2 months ago (1 children)

Store your database in a nextcloud instance and it's that too

[–] unrushed233@lemmings.world 2 points 2 months ago (1 children)

Nope. Since the entire database is contained in a single file, it can't sync multiple edits properly, leading to sync conflicts. Because KeePass was built around local database files, whereas Bitwarden uses actual synced databases, where individual updates can be uploaded, instead of causing conflicts or overwriting the entire db.

[–] Hexarei@programming.dev 1 points 2 months ago (1 children)

Conflicts haven't been an issue for years, all modern iterations of KeePass (XC, kp2a, DX) support automatically merging in the latest before saving.

I've been using it for years this way across several devices, it's incredibly solid

[–] Dymonika@beehaw.org 2 points 1 month ago (1 children)

Do you sync it across your devices using Syncthing? That's what I'm thinking of doing.

[–] Hexarei@programming.dev 1 points 1 month ago

I keep mine in a self hosted Nextcloud instance, DAV sync is built into the app