3 ms·

Can somebody ELI5?

• wmf 2y ago
  AFAIK they went closed source the other day which triggered backlash and now they're opening back up.
  • jth1 2y ago
    My understanding is they were never closed source. Some of their code is GPL and some is proprietary, but all is source-available on GitHub. There was a bug where you couldn't build their client without a proprietary dependency, but they have fixed that so you can now build their client with only GPL code again.
    • palata 2y ago
      I don't think it was a bug. They dismissed it and clearly said that they had no intention to adjust the license: https://github.com/bitwarden/sdk/issues/898 https://github.com/bitwarden/sdk/issues/898.
      • renewiltord 2y ago
        To be honest, it looks like he just had an internal model of “internal code no gpl”, “external code gpl” and mindlessly answered based on that. The fact that it made the latter impossible seems to have been successfully impressed on him. Overall, I’ll stay a Bitwarden customer. People fuck up and I’m a tit-for-tat-with-random-forgiveness tactic user, not grim-trigger.
        • palata 2y ago
          I could accept that he doesn't understand how open source licenses work, or doesn't care, and that it was not meant as a shady move. But still I wouldn't call it a bug, and it does not inspire confidence. Still it's not LastPass-bad. This said, I still recommend Bitwarden to my family. I moved to pass (https://www.passwordstore.org/ https://www.passwordstore.org/) a while ago just because it corresponds better to my needs and I have more control.
• chx 2y ago
  People are dicks to one of the last companies which operate in a transparent manner and open source their product. There was a bug, it got fixed. Nothing to see here, move along.
  • palata 2y ago
    This doesn't look like a bug: https://github.com/bitwarden/sdk/issues/898 https://github.com/bitwarden/sdk/issues/898