Comment on Bitwarden Switches to Commercial License
thr0w4w4y2@sh.itjust.works 2 weeks agoit literally says in the post that the license change affects companies who are repackaging and reselling bitwarden, but ok.
Comment on Bitwarden Switches to Commercial License
thr0w4w4y2@sh.itjust.works 2 weeks agoit literally says in the post that the license change affects companies who are repackaging and reselling bitwarden, but ok.
nibbler@discuss.tchncs.de 2 weeks ago
But this is the post by bitwarden, defending their decision. AKA marketing.
Can you explain how bitwarden can be “repackaged and resold”, that would be stopped by that change?
Everybody can still fork/rename/publish the FOSS version which is continued to be available. Everybody can connect to vaultwarden…?
Buckshot@programming.dev 2 weeks ago
Yeah this only makes sense if the builds start diverging from the open source code, extra features that are closed source.
lemmyvore@feddit.nl 2 weeks ago
Yeah, but there’s no guarantee the FOSS version will be the same as the closed one.
nibbler@discuss.tchncs.de 2 weeks ago
There is certainty that the Foss version won’t be worse than current bitwarden client. Then those will diverge. So?
lemmyvore@feddit.nl 2 weeks 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.