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.

    • unrushed233@lemmings.world
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      2 months ago

      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
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        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
          link
          fedilink
          arrow-up
          1
          ·
          1 month ago

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