- cross-posted to:
- linux@lemmy.ml
- cross-posted to:
- linux@lemmy.ml
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.
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.
Just tried it, and it seems you can’t edit or add items without a premium subscription??
Or am I missing something?
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.
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
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?
It would be if it’s a one-time payment, but it’s a yearly subscription, and not a cheap one!