this post was submitted on 20 Oct 2024
627 points (87.4% liked)

Technology

60062 readers
4459 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 2 months ago (1 children)
[–] [email protected] 21 points 2 months ago (3 children)

They now require a non-free Bitwarden SDK component. That's what this whole conversation is about.

[–] [email protected] 2 points 2 months ago (1 children)
[–] [email protected] 7 points 2 months ago

"You may not use this SDK to develop applications for use with software other than Bitwarden (including non-compatible implementations of Bitwarden) or to develop another SDK."

This is a condition when using their SDK. This is not considered a free (as in freedom) component because it violates freedom 0: https://www.gnu.org/philosophy/free-sw.en.html#four-freedoms

[–] [email protected] 2 points 2 months ago

And the whole conversation is about a bug, not a change in direction...

Update: Bitwarden posted to X this evening to reaffirm that it's a "packaging bug" and that "Bitwarden remains committed to the open source licensing model."

[–] [email protected] 1 points 2 months ago

Only the desktop client. And the response is that not being able to compile sans SDK is an issue they will resolve.

I still think this is bad directionally, but we need to see what happens.