Magnus Åhall
System/web/Linux developer
Phew, looks good on the news with the packaging bug (if they didn’t just got cold feet for worse PR/backlash than they expected and this is a backtracking).
In this case, hopefully Garcia is employed for his expertise and can be deployed to further open source relations :)
I’m running a couple of Vaultwarden instances, and it would be really nice if Bitwarden employed Garcia to improve the Rust backend. But as the bitter cynic I am, I guess it is an effort to shut down and control as much of the open source use of Bitwarden as possible.
The worst case, someone will most likely fork Vaultwarden and we can still access it with Keyguard on mobile and the excellent Vaultwarden web interface :)
Daniel García, owner of the Vaultwarden repo, has recently taken employment for Bitwarden.
The plot thickens.
We have had the opposite problem in the past. A cert provider requiring us to exist in certain international directories of companies took weeks of waiting around on bureaucratic red tape.
Then they didn’t even call us to verify our existance, place of business or anything (yeah, this was one of the big certificate providers a long time ago).
Their website was horrible, and their support wasn’t better.
LetsEncrypt though hasn’t failed me once since it was setup, and that is over hundreds of domains with thousands of renewals.
The Kame ipsec project (https://www.kame.net) has a turtle image which is animated if visited with an IPv6 address.
Not exactly that layout, but I can strongly recommend MessagEase. Also optimized for phone use.
What if they DIDN’T have a chip in the ink cartridge, and just used it as a container that could be refilled and used in every printer they made? No hacking the cartridge then.
No, that’s crazy talk!