Gregory's ServerThe first rule of #Enshittification is that proper lock-in cannot occur if the product is thriving as Open Source, so once you've reached sufficiently high switching costs, pull out the rug.
 10 comments
@jschauma and stop people from discussing it (in this case, the issue was locked). Also, see https://github.com/bitwarden/sdk/issues/898, where this was initially reported, and which was promptly closed by BW. It is probably time to find a replacement, or maybe someone with the ressources and will will start a freewarden... @jschauma by the way, like the universe trying to tell me something, I just heard about https://www.passbolt.com a few hours ago... As far as I understand the GPL'ed their SDK by distributing them together. Also GPLv3. LOL.  @jschauma considering the fact that #BitWarden was never #FLOSS to begin with (unlike #KeePassXC & #KeePassDX!) I'm not surprised.   @jschauma According to this statement from Bitwarden on Twitter, it wasn’t intentional: https://xcancel.com/bitwarden/status/1848135725663076446 I hope that's true, but it seems unlikely it was just an accident, given they're comfortable with not being on fdroid: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/15353#note_1995132756  @jschauma@mstdn.social |
@jschauma This might explains why the mobile app is having trouble with my Vaultwarden instance…
Shit…