The issue is that when people reply to my tweets, they are trying to use my audience to push their message. If they have their own followers, OK: that's them talking to their people. But they want to talk to my audience. And they might have something shitty or spammy to say, and their coming back to my threads to say it hurts my ability to communicate with my audience.
So, Twitter finally gave us a feature to hide these replies, which was almost great... except somehow it does the opposite?! It takes the message, which might have, in practice, been semi-buried in a pile of a hundred replies, and elevates it by giving the hidden replies a special icon and their own panel. I wanted to hide the hate speech, not feature it!
To make it even more ridiculous, users often get a pop-up a box to remind then "hey you can find the hidden replies here"... it frankly totally undermines the point of the feature. If I hid it, it should be hidden... at least from people who started from my tweets, and at least if they don't follow the person who posted the message (I don't want to limit the ability for people to communicate with their own followers).
(FWIW, I hopefully-clearly totally feel for the premise that Twitter should be something of a utility and that people should get to communicate with people who opted-in to what they had to say, but this ability to reply to someone else's message isn't that. If you have further consistency issues with my premise, I will note that in a system I would personally design, all replies would be hidden by default and users would have to manually mark them as visible to their audience, at which point they would take on the moral responsibility for the content, at which point I believe you could have truly uncensored follower-to-user and user-to-follower interaction, which I think should be a goal. I only really say any of this, though, to make my complaint consistent with my past complaints: I currently consider the premise of this complaint to stand-alone and be consistent with itself given the reason this feature theoretically exists, which it seems to not satisfy... it was like a half-assed mistake of a mitigation, and now we are seeing them start to play whack-a-mole.)