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.

  • Bilb!@lem.monster
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 month ago

    I have some! I use a self hosted vaultwarden and just two days ago I saw and installed KeyGuard out of curiosity. So far, I can say KeyGuard is a nicer looking and feeling app and… it works. So as long as their intentions are pure, you can use “bitwarden” without using any of their software or infrastructure.

      • Bilb!@lem.monster
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        1 month ago

        Ah, yeah, I installed it from their github with obtainium. I think open source/libre app that charges prior to install with the play store is a model a few others have tried as well.

        • smiletolerantly@awful.systems
          link
          fedilink
          arrow-up
          4
          ·
          1 month ago

          I don’t think it’s unreasonable to want to be paid, but a mandatory subscription when using the most common install method does irk me the wrong way

          • Bilb!@lem.monster
            link
            fedilink
            English
            arrow-up
            4
            ·
            1 month ago

            I haven’t looked into it at all, but that just seems so strange. Who would pay that when the original Bitwarden app is still there for free? Most people who would even know about KeyGuard would know how to install it from somewhere else. Is it essentially a donation?