Just a moment...
www.theregister.com

Bitwarden isn’t going proprietary after all. The company has changed its license terms once again – but this time, it has switched the license of its software development kit from its own homegrown one to version three of the GPL instead.

The move comes just weeks after we reported that it wasn’t strictly FOSS any more. At the time, the company claimed that this was just a mistake in how it packaged up its software, saying on Twitter:

It seems like a packaging bug was misunderstood as something more, and the team plans to resolve it. Bitwarden remains committed to the open source licensing model in place for years, along with retaining a fully featured free version for individual users.

Now it’s followed through on this. A GitHub commit entitled “Improve licensing language” changes the licensing on the company’s SDK from its own license to the unmodified GPL3.

Previously, if you removed the internal SDK, it was no longer possible to build the publicly available source code without errors. Now the publicly available SDK is GPL3 and you can get and build the whole thing.

  • penquin@lemm.eeEnglish
    1966·
    8 days ago

    Call me cynical, but I don’t think it was a “packaging bug”. I think they felt the backlash from their users. I mean, it’s still great and now I’ll go back to using their app.

      • penquin@lemm.eeEnglish
        14·
        7 days ago

        Cry me a river. Fucking internet weebs, one can’t even express their opinion without everyone whining about it. Lmao.

        • Abnorc@lemm.eeEnglish
          2·
          6 days ago

          You can express your opinion, but other people can criticize it. It’s just how these sites work.

        • frayedpickles@lemmy.cafeEnglish
          22·
          7 days ago

          You literally asked us to call you cynical, dumdum. Why are you asking for something and then getting butthurt when it’s provided? That’s what toddlers do.

    • BearOfaTime@lemm.eeEnglish
      35·
      8 days ago

      There was a really good explanation by a rando about how it happened. Seems a dev made a mistake when publishing a change.

      Apparently bitwarden immediately changed internal procedure for publishing changes.

    • Bezier@suppo.fiEnglish
      6·
      8 days ago

      I expected the same by default, but after learning more I find it unlikely. They had a pretty good explanation for it being a mistake.