this post was submitted on 05 Nov 2024
486 points (98.6% liked)

Technology

59495 readers
3110 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] schizo@forum.uncomfortable.business 301 points 2 weeks ago (10 children)

Wow, a commercial open source product that COULD have pulled a rugpull, looked for all the world like they were planning a rugpull, just uh, did the right thing?

Good job, Bitwarden.

[–] octopus_ink@lemmy.ml 52 points 2 weeks ago (6 children)

I'm sure all the folks who were quick to ignore or dismiss their clarification of the packaging issue at the time will be just as quick to make comments like these as they were to skewer them then.

[–] sugar_in_your_tea@sh.itjust.works 7 points 2 weeks ago* (last edited 2 weeks ago) (5 children)

I tried convincing people to give them the benefit of the doubt and see what they do, but no, everyone seemed to jump to conclusions.

Glad my trust wasn't misplaced this time. I have been and continue to be a paying customer.

[–] Llewellyn@lemm.ee 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

but no, everyone seemed to jump to conclusions

And I'm certain that it has served as the catalyst for the bitwarden decision.

[–] sugar_in_your_tea@sh.itjust.works 1 points 2 weeks ago* (last edited 2 weeks ago)

I disagree, but unfortunately, we will probably never know. That said, I'm not against the outrage, I'm just against the conclusions. You don't need to immediately abandon a project at the slightest hint they're moving in a direction you don't like, what you should do is start watching that project a bit more closely to see if they correct or they make additional changes you don't like.

We should be taking the rational approach instead of the reactionary approach, but social media in general seems to love reacting instead. I've abandoned projects that went a direction I don't like, but I usually give them a few months after the first sign of problems. I'm currently doing that w/ Mozilla and I want to see what they do with their advertising push before jumping ship.

load more comments (3 replies)
load more comments (3 replies)
load more comments (6 replies)