this post was submitted on 26 Oct 2024
314 points (97.0% liked)
Technology
59377 readers
5695 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- 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
view the rest of the comments
If that wasn't on purpose than that was a big fuckup. I was sometimes thinking about testing Bitwarden but with this volatile license situation I'm not interested anymore.
That's a poor understanding of the situation. Nothing in the licensing changed. The SDK has always been the proprietary business to business secrets management product. The client integrates with and can use that SDK to provide the paid service to businesses. The client and the server side management of password has always been and still is FOSS.
This was apparently an accidental change in the build code (not the client code, just the building scripts) that required the inclusion of the SDK to build the client when actually it has never and doesn't really need any of that code. It prevented building the client without accepting the SDK license. Which it shouldn't.
This was fixed and some things will be put in place so it doesn't happen again. Nothing in the licensing scheme changed, at all. This is not a catastrophic enshittification event. A Dev was just being lazy and forgot to check the dependencies on the build chain before their commit.
And, amazingly, someone still downvoted you.
Idiots downvoting amazes you? Then there's a whole world of amazement awaiting you!