It'll be interesting to (if that ever happens) see whether bluesky, once it actually becomes a decentralized system instead of a closed one, shakes out differently due to protocol differences, or broadly follows the same patterns.

It is also at the same time contrary to everything he‘s said before about how he would run twitter - hell, he called this account out specifically as one he would not ban because he is oh so committed to free speech.

It will also not be enforced against anyone except if you‘re sharing the location of Elon, of a billionaire buddy of his, or kick up enough of a stink that it‘s a PR issue.

Other than that, well, there really isn't a downside, so yeah, why not.

On our instance, we do not allow "untagged" (not hidden behind a content warning) pornographic content. If an instance allows this, we "silence" them - meaning that none of their content shows up on any public timeline anymore. People can still follow users from there, but that's their choice, and none of my business - and nobody is getting a facefull of tiddy if they don't specifically want it.

If an instance is generally acting in good faith, but allows images that I definitely do not want cached locally, another tool you have is "media reject" an instance - in that case, no media from that instance will be downloaded. Can still follow, but have to click through for images, and no thumbnails. We try to avoid this, but, you know.

The nuclear option is to just defederate from an instance entirely. We also try to avoid this, but it's a very effectice "ugh god I'm not dealing with this" tool.

edit: That's on a macro level, of course - we can also do the same thing to single users, and that's obviously preferred if it's just one idiot. a user submitting a report can also choose to forward the report the the originating server, which can be helpful to get a problem at the root.

You can always join a place where the credo is "we connect with everybody", while people who want a very filtered experience can join places that are a lot more nonchalant about blocking other instances. A lot of people probably do (and want to be in a place that does) something in the middle.

You could even have multiple accounts on different instances that you use in different contexts. Most mobile clients support this more or less well, though the default web UI does not.

Twitter, as a company, seems to assume that the former is the default. I don't know if the majority of their users are actually like that. The vast majority of my tweets is replies to other people, and for most people I know it is the same, but of course, self-selection would do that. The analogy as twitter being unrolled IRC is, for me, definitely how I've been thinking of it for years.