asudox@programming.dev to Technology@lemmy.worldEnglish · 9 days agoConcerns Raised Over Bitwarden Moving Further Away From Open-Sourcewww.phoronix.comexternal-linkmessage-square113fedilinkarrow-up147arrow-down120 cross-posted to: [email protected]
arrow-up127arrow-down1external-linkConcerns Raised Over Bitwarden Moving Further Away From Open-Sourcewww.phoronix.comasudox@programming.dev to Technology@lemmy.worldEnglish · 9 days agomessage-square113fedilink cross-posted to: [email protected]
minus-squarer00ty@kbin.lifelinkfedilinkarrow-up2·9 days agoIf they’re moving away from open source/more monetisation then they’re going to do one of two things. 1: Make the client incompatible (e.g you’ll need to get hold of and prevent updating of a current client). 2: DMCA the vaultwarden repo If they’re going all-in on a cash grab, they’re not going to make it easy for you to get a free version.
minus-squareschizo@forum.uncomfortable.businesslinkfedilinkEnglisharrow-up2·9 days agoDon’t forget option 3: someone writes a vaultwarden client independent of the closed-source crap. If you can write a server that fully supports the client via the documented API, then you know everything you’d need to do to make a client as well.
minus-squarepotustheplant@feddit.nllinkfedilinkEnglisharrow-up1·9 days agoYou can’t “dmca” the fork that was created while it was still open source. They could only prevent it from getting future updates (directly from them).
If they’re moving away from open source/more monetisation then they’re going to do one of two things.
1: Make the client incompatible (e.g you’ll need to get hold of and prevent updating of a current client).
2: DMCA the vaultwarden repo
If they’re going all-in on a cash grab, they’re not going to make it easy for you to get a free version.
Don’t forget option 3: someone writes a vaultwarden client independent of the closed-source crap.
If you can write a server that fully supports the client via the documented API, then you know everything you’d need to do to make a client as well.
You can’t “dmca” the fork that was created while it was still open source. They could only prevent it from getting future updates (directly from them).