Do you have a source on that?
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.
Link doesn't work
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?"
If we find instances infested with bots and unwilling to deal with them, we defederate them. It at least makes it more difficult to mass-infest the network with bots if we have basic things like captcha, email verification, and applications implemented in all the major instances. cough
This fediverse at least. AT Protocol, used for bluesky, supports nomadic identity. Instead of accounts being @[email protected], they attach your domain / home instance / whatever, to a DID. You can read more about it in their various spec pages but here's the one for DIDs.
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.
Don't fill in this field, that turns your instance into a whitelist server. Remove everything from the allowed instances list
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.
idk I quite like the changes he's making. Rate limiting, preventing people who don't sign up from using it, killing embeds. It's all great for reducing the net presence of what has become an almost entirely white nationalist platform. If anything he's not rolling out these changes fast enough, for if he was, Twitter would have also restricted itself from having new sign ups (like Voat in its later years) and eventually completely shutting down.
AT Protocol can do this in the way of DNS DIDs, but ActivityPub doesn't have this functionality.
It looks like you already have federation enabled, but if you're having troubles you're probably best off going to [the support community for assistance at [email protected]
Never banned. Left because I disliked the moderation, the community at large, and the content that rose to the top of their algos.
Because the redneck themed one wants to call queer people groomers and have them sentenced to death by firing squad.
There's also many small-to-medium sized instances that just haven't bothered signing that will be defederating. Mastodon.social's gonna be one of the few who do, and I already think it's fine to defederate from them too tbh.
Meta's fine with transphobia. I am not. It can hardly be called a decision at that point, I don't need Libs of Titkok and their ilk filling my federated feed.
