It’s the heavy machinery required to do it that’s the problem. This is also not Elon Musk’s building, but a building Twitter rents. The building management company were the ones who called the police.
It’s the heavy machinery required to do it that’s the problem. This is also not Elon Musk’s building, but a building Twitter rents. The building management company were the ones who called the police.
a lot of hate for capitalism here
The fediverse is largely populated by 2SLGBTQIA+ people and people of colour who are oppressed by capitalist regimes. The other big contingent is marxists and people who like FOSS. FOSS, at its core, is anti-capitalist.
You’re in a place founded by anti-capitalism, that exists in spite of capitalism, asking “why is there so much anti-capitalism here?”
Nuke Studio
Bitwarden only autofills if the page’s URL is the same as the account in your vault. So it actually helps you make sure that you aren’t putting your info into a phishing site or something
This is true, though wasn’t my concern. My concern is that it (and other PW managers ofc) can sometimes fill in fields its not supposed to, and you end up accidentally including a username or password in a GET header.
although, I’m pretty sure autofill is disabled by default anyway?
Auto-fill on page-load is, yes.
Bitwarden checks all the boxes. I’ve had great experience with it. https://bitwarden.com/
I will say, auto-fill on load is a bad idea. On desktop I keep my auto-fill bound to a key so it doesn’t actually end up in fields it shouldn’t be.
2FA is locked behind the $10/year premium if that’s something you wanted, but beyond that the free plan has everything 99% of people will use. They do third party security audits, have public white papers, and is completely open source.
I’d recommend anyone using this to really consider how much data this’ll use on their system.
Do you have a source on that?