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.
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…
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.
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…
From what I understand there was also a bug involved that caused build failures without the sdk.