this post was submitted on 20 Oct 2024
623 points (87.5% liked)

Technology

58813 readers
4844 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
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 23 hours ago (1 children)

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."

I'm not going to jump ship just yet, though I may get around to updating my backup.

There are plenty of alternatives, so feel free to shop around. But don't jump the gun just because of a random Phoronix article with an update that says basically the opposite of what the article claims. Wait some time to see if there are actual changes coming.

[–] [email protected] 0 points 22 hours ago (1 children)

Yeah no. This is clearly backpedaling and you should look to get away

[–] [email protected] 2 points 22 hours ago

Maybe. Here's what they say in the readme of the project people are complaining about:

The password manager SDK is not intended for public use and is not supported by Bitwarden at this stage. It is solely intended to centralize the business logic and to provide a single source of truth for the internal applications. As the SDK evolves into a more stable and feature complete state we will re-evaluate the possibility of publishing stable bindings for the public. The password manager interface is unstable and will change without warning.

There are two ways to take this:

  • this is temporary as they're refactoring code to reduce duplication across clients
  • refactoring is an excuse to create fully proprietary clients going forward

Until I see evidence of the latter, I'll stick with the project, but I'll be more consistent about creating backups so I can switch easily if I need to.