• @[email protected]
    link
    fedilink
    English
    2114 hours ago

    I love Bitwarden… I read the article, but is this something I need to feel concerned about? I also just started using their Authenticator app a few months ago, so this had a given me a pit in my stomach. What should I do?

    • @RockaiE
      link
      English
      2314 hours ago

      With what we know, there nothing to be worried about. The issue lies with the Bitwarden SDK, and not the Bitwarden apps or authenticator. The language is not entirely clear, but my interpretation is that they want to prevent people from using the SDK to create a Bitwarden app competitor. It sounds like they do want businesses to create their own, internally used client, and worded the TOS in a confusing way.

      • @visor841
        link
        English
        1
        edit-2
        6 hours ago

        From what I understand there was also a bug involved that caused build failures without the sdk.

      • @[email protected]
        link
        fedilink
        English
        413 hours ago

        Thank you for your reply. It does make me feel a little better. I’ll keep an eye out in case they continue to shift towards enshittification I suppose…

    • @[email protected]
      link
      fedilink
      English
      813 hours ago

      It’s a minor, technical change to the license. It’s not a change we should be supporting but it doesn’t matter much. The real concerning thing is that this may signal a shift away from focusing on the value to the user.

      • @[email protected]
        link
        fedilink
        English
        212 hours ago

        Thank you for the reply. I was worried about the shifting. I’ll keep my eye on any other news that comes out with them. Sigh…