This is literally why twitter is bad (well, one of several reasons).
On a lot of social media sites, there’s this perennially discussed issue where people will post e.g. some article with a clickbait headline, and everyone will start yelling at each other in the comments without even having looked at the contents of the article, basing their anger purely over what they guess is in it based on the headline. Because the number of words you can fit in a headline is perfectly optimized to be attention grabbing, while also excluding as many important details as possible so that you’re still enticed to click the link. Of course, a side effect of this is that if someone doesn’t click the link, if they decide they just can’t be bothered, then the headline has given them just enough information to be mad about while giving them too little information to actually know what claim is being made in any detail. So they get mad at the claim they imagine is being made, i.e. the most strawmanned and cartoonishly evil version of whatever their opponent is saying.
Ok, so now imagine that someone designed a social media site where literally, structurally, every post is nothing but a clickbait headline. No article to go with it, nothing you can turn to for elaboration. Just the inflammatory and informationless bit, nothing else. If you want to catch people’s eye in 280 characters, you have to either shock them or piss them off, and since you’ve only got 280 characters, there’s no room to explain yourself afterwords. You might say that threads provide a solution to this, but threads are cumbersome to navigate and split text up in a restrictive way that makes both writing and reading long and detailed thoughts quite difficult. A twitter thread invariably makes you feel like you’re reading more than you actually are, because of the way it’s formatted. But the amount you can communicate is still starkly limited by the structure.
Anyway, yeah, that’s twitter: Not Reading The Article Simulator 2006.