Edit: it actually disappeared for some time but they put it back on May 18
snapshot from May 15: https://web.archive.org/web/20260515190646/https://bitwarden...
snapshot from May 18: https://web.archive.org/web/20260518183728/https://bitwarden...
Edit: it actually disappeared for some time but they put it back on May 18
snapshot from May 15: https://web.archive.org/web/20260515190646/https://bitwarden...
snapshot from May 18: https://web.archive.org/web/20260518183728/https://bitwarden...
There are a fair amount of multi-hundred year old companies out there.
No it absolutely must not.
When a company tells you their intention by announcing a change, it's often a good idea to listen. Even if their PR department does some good cleanup work in the aftermath.
Another recent example is GitHub charging for self-hosted CI. They backtracked, but they're still going to end up doing something. They kind of have to because of all the "get 10x cheaper actions runners by changing one line" people.
If they are going to make it not free, they can just remove it right before they make it not free.
If it was somehow a binding promise, then it doesn’t matter if they remove it or not, the promise was already made.
If it isn’t a binding promise, then it doesn’t matter if they remove it or not, the promise was not binding anyway.
i think this is the overreaction - getting worked up about these sort of risks in general isn’t worth your time.
Otherwise you’d end up self-hosting everything strictly on OSS from maintainers you personally know and trust.
This is like someone saying, “don’t use AWS because they might raise prices some day”
Between the law suits, and the brand damage, there is likely very little upside for a company entertaining this idea.
> The “Always free” motto quietly reappeared on the site after its removal was uncovered and went viral on Fedi.
(And the linked article gives evidence: <https://blog.ppb1701.com/the-quiet-renovation-at-bitwarden#:...>.)
Nah, I think I'll stick with and keep paying/supporting Bitwarden.