this post was submitted on 05 Nov 2024
406 points (99.0% liked)
Technology
59120 readers
2611 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
Call me cynical, but I don't think it was a "packaging bug". I think they felt the backlash from their users. I mean, it's still great and now I'll go back to using their app.
You're cynical, and worse, in a way that is unproductive.
I expected the same by default, but after learning more I find it unlikely. They had a pretty good explanation for it being a mistake.
Never attribute to malice what can just as easily be explained by incompetence.
Or just wanting to get done with the day and pushing to last commit.
Yeah..
Yup, just replace "incompetence" w/ "laziness" or whatever and you'll be right much of the time.
Imagine being unable to do any mistake in a larger org.
There was a really good explanation by a rando about how it happened. Seems a dev made a mistake when publishing a change.
Apparently bitwarden immediately changed internal procedure for publishing changes.