Comment on Bitwarden Switches to Commercial License
nibbler@discuss.tchncs.de 6 days agoThe back end is already solved by vaultwarden, so I’m not sure what you mean
Comment on Bitwarden Switches to Commercial License
nibbler@discuss.tchncs.de 6 days agoThe back end is already solved by vaultwarden, so I’m not sure what you mean
lemmyvore@feddit.nl 6 days ago
Both backend and frontend revolve around the API, and Bitwarden owns that not Vaultwarden.
If Bitwarden decides to modify the API so that only their closed-source backend has the full spec, and only gives that spec to their own apps, everything else (Vaultwarden and 3rd-party apps) will fall behind or become unusable.
nibbler@discuss.tchncs.de 6 days ago
The api is implemented in Foss front&back end… I don’t know what you are talking about
lemmyvore@feddit.nl 6 days ago
If there are two version of Bitwarden backend (closed and FOSS), and the closed one changes its API, and the closed Bitwarden apps also switch to the closed API, then what value does the FOSS API have anymore?
nibbler@discuss.tchncs.de 6 days ago
What is “the API”?
The API is implemented by the bitwarden back end.
The API is also implemented by the vaultwarden back end.
The open source bitwarden client does talk the current version of this API. The open source client can be forked, so there is without much effort a version speaking this protocol in this version and is FOSS. Just the name will be different. I guess “vaultwarden client” would be fitting, but what ever.