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

Technology

59123 readers
2973 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] 214 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

This is an important issue IMO that needs to be addressed and the official response by Bitwardens CTO fails to do so.

There is not even a reason provided why such a proprietary license is deemed necessary for the SDK. Furthermore this wasn’t proactively communicated but noticed by users. The locking of the Github Issue indicates that discussion isn’t desired and further communication is not to be expected.

It is a step in the wrong direction after having accepted Venture Capital funding, which already put Bitwardens opensource future in doubt for many users.

This is another step in the wrong direction for a company that proudly uses the opensource slogan.

[–] [email protected] 101 points 2 weeks ago (2 children)

nothing lasts forever without being enshittified

[–] [email protected] 5 points 2 weeks ago

not in capitalism no

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

Except if it's free software.

[–] [email protected] 64 points 2 weeks ago (2 children)

Welp, I guess another time to move here soon.

And I just fucking vouched for them to a friend recently 🤡

Didn't know about VC funding these parasites using their funding to turn everything into shite.

What's the current "best" alternative? Keepass?

[–] [email protected] 17 points 2 weeks ago (1 children)

I haven't jumped yet, but the Proton suite is looking more and more appealing. I've been eyeing them as a Gmail replacement, but I've been happy with my VPN and password management providers. As this reduces the bundle makes more sense.

[–] [email protected] 29 points 2 weeks ago (2 children)

They have a solid value proposition but don't like putting all my eggs all in one basket both for security and monopoly reasons.

They seem to be gunning for one stop shop and I think they are doing decent shop but I just don't like the idea after what Google did to us.

Situation is a bit different but gonna need to tka the lessons and not let these corpos do this again.

[–] [email protected] 7 points 2 weeks ago

That's a good practice, and I think you're right that is what they're going for. I don't think that means you shouldn't consider them, but it does lower their value proposition as the bundle is the better deal.

[–] [email protected] 1 points 2 weeks ago* (last edited 2 weeks ago)

this isnt a full solution obviously, but I figured it'd be nice to know: Proton lets you set different passwords for your email and password manager, so at least from a security standpoint its not all behind the same password, even if it is still from the same company

[–] [email protected] 1 points 2 weeks ago* (last edited 2 weeks ago)

It's not open source, but I got a lifetime license for Enpass over a decade ago and it's done everything I've ever needed it for. I think stacksocial occasionally has new lifetime codes for sale. I like the idea of Proton Pass as others have said, but it feels a bit like putting all my eggs in one basket, which is a mistake I already made with Google before (context: I use Proton for email). I think Keepass is the next best option if dedicated to staying FOSS.

[–] [email protected] 11 points 2 weeks ago

They're basically trying to get rid of vaultwarden and other open source forks. I expect they'll get a cease and desist and be removed from github at some point in the not too distant future if they don't make some changes. I have a vaultwarden instance and use the bit warden clients. Guess I'll need to look for alternatives in case Bitwarden decides to get aggressive.