You don't want to interact with me? Fine. Then why should I still see your posts? Yes, some crazy people will go to lengths to see it anyway, but most don't and will take the hint, shrug, and go away.
https://www.reddit.com/r/EnoughMuskSpam/comments/1fnvt8n/elo...
Feel free to steel man and tell me why you think it's useful. I think the friction it causes is cancelled out by the effect of annoying the mostly well-meaning portion of the people who are blocked while not annoying the truly toxic users who will quickly and easily bypass it at all.
I don't tend to participate in twitter fights. A type of twitter fight that comes to mind is people who work at FAANGs being annoyed that people are criticizing their employer's agenda. I saw this against Google with AMP and with Chrome hiding the path from the address bar in a dev channel release. That isn't really coming out of a place of toxicity. The complainer doesn't really deserve to be blocked, but the FAANG employee has a right to keep their mentions and reply threads clean. For minor scuffles like these, a lighter form of blocking is nice.
If you're blocked by prolific reply guys in your circle, you regularly have to not just scroll past their censored replies at the top of the reply section, but you see other people's replies to them which compels you to switch accounts to see what dumb thing they said this time. And now you can simply reply to them on your other account.
Twitter ossified their feature set a long time ago, which is not surprising because "stick with what made us big" is a reasonable course of action. In that sense great diversity and more experimentation in different approached with Threads, BlueSky, and Mastodon is generally a good thing (even though I don't really use any of them, mostly out of laziness).
> No it doesn't.
There's really no use in continuing this discussion when one party is unable/unwilling to use precise language to discuss marginal effects. Obviously I presume what you mean is that the marginal effect is too small to be relevant, but discussions with people who round that off to "No it doesn't" rarely go anywhere productive.
No and nobody claimed it does. Making it just a bit harder and making the other party jump through an extra hoop reduces it though. The extra friction has been implemented on many platforms and it works. Instagram adds friction in a different way, but also claims it has a positive result: https://builtin.com/software-engineering-perspectives/key-be...
You can also see people migrating to other platforms who raise the lack of search / being easily found as a feature. It's not black and white and it's not public or not. There's a whole range of how accessible your content is to parties who will attack you.
It might have not been ideologically consistent but it was effective.
For example, if all they know is the app, they may even think you NEED the app to see posts, or that you CAN'T create multiple accounts on the same app because they signed up with their phone number instead of e-mail.
Just like the smallest UI hurdle blocks onboarding users, the smallest UI hurdle also stop malicious behavior.
Not every malicious user is the hacker type. Sometimes it's just someone stalking their ex-partner. The malicious user could be an elder, could be a teenager, they could be from the U.S. but they could also be from Africa.
When you consider non-English speaking countries, expertise drops tremendously because any high level information is kept behind a language barrier.
Either your posts are public or they're not. There's a pretty clear distinction between the two, and anyone who thinks otherwise is sorely mistaken. The risk of people re-posting your content is a natural consequence of your aspirations to be popular on social media, and we shouldn't be giving people a false sense of security.