Comment on Bitwarden Switches to Commercial License
nibbler@discuss.tchncs.de 6 days agoThere is certainty that the Foss version won’t be worse than current bitwarden client. Then those will diverge. So?
Comment on Bitwarden Switches to Commercial License
nibbler@discuss.tchncs.de 6 days agoThere is certainty that the Foss version won’t be worse than current bitwarden client. Then those will diverge. So?
lemmyvore@feddit.nl 6 days ago
The current FOSS backend used to be the center of the ecosystem. Going forward that may change. If it stops being that center and it becomes merely a token offering so Bitwarden can claim “we’re still doing FOSS” then it will become pointless.
Simply forking the backend is meaningless without the work to also drag along the entire ecosystem, or establish a new one. Forking a project takes time, effort, vision, persistence, determination.
nibbler@discuss.tchncs.de 6 days ago
The 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