I have the same feelings about it. For now, the system does function very well.
Comment on Self-hosted keypass fork recommendation
zikzak025@lemmy.world 5 days agoJust don’t count on the current Bitwarden client being compatible with VaultWarden forever. Bitwarden’s new CEO is pushing to make more profit wherever possible, and recently rescinded the statement from the company’s website that the client would be free forever.
They’ll never be able to walk back the open source nature of the product, but they can choose to make their client incompatible with VaultWarden and push for the centrally hosted option as the only option.
Not sure if anyone’s forked the Bitwarden client yet, but that’s how I’d start using VaultWarden if the option exists.
Or, you know, skip the headache and just start using Keepass.
altphoto@lemmy.today 5 days ago
45o3b@lemmy.ml 4 days ago
It looks like there are 1900 forks on GitHub.