Re:Bitwarden SDK relicensed from proprietary to GPLv3
by cmeacham98 on Friday October 25, 2024 @10:40AM
(#41945719)
Your comment was marked dead FYI, I vouched for it.
Normally this would mean you are shadow banned, but I don't see any other comments in your history getting this treatment - perhaps this comment caught the ire of some anti-spam algorithm.
Re:Bitwarden SDK relicensed from proprietary to GPLv3
by xelamonster on Friday October 25, 2024 @12:24PM
(#41946791)
I mean it reads like ad copy, and the entire first paragraph takes so many words to say nothing more than "I agree." As comments go, I have to say I've seen better.
Re:Bitwarden SDK relicensed from proprietary to GPLv3
by Brian_K_White on Friday October 25, 2024 @01:43PM
(#41947598)
I got more out of it than this one.
Re:Bitwarden SDK relicensed from proprietary to GPLv3
by hedora on Friday October 25, 2024 @10:46AM
(#41945775)
Old versions of vaultwarden broke recently (for just about everyone?) due to incompatible changes on the iOS client.
Breakage is not ideal, but here's how they handled the second, more subtle compatibility break:
https://github.com/dani-garcia/vaultwarden/issues/5069
I haven't worked up the courage / time to back up my database and upgrade the docker container; will probably get to it this weekend. However, I can't imagine using bitwarden with the official server (too bloated to be trustworthy), or with their cloud thing. I got burnt by lastpass. I'm not putting my passwords in a giant high-value target again.
Backups are also fairly easy so if need be a DR can be done (and automated) with very little hassle. The vaultwarden backend does depend upon the bitwarden apps for client devices but also features it's own web UI.