[miki123211]

Blocking doesn't really fix the brigading problem, regardless of whether people need to log out or not.

Most X users will just post a screenshot of the tweet, breaking accessibility in the process and disassociating the original author from the thread against their will.

This isn't always a good thing, as it leads to people being surprised by crowds of strangers suddenly screaming at them and not being able to see the source of their anger.

Some people do this as a "preventative measure", so that their post still makes sense when the original tweet is deleted.

[raydev]

> Blocking doesn't really fix the brigading problem

Automated blocking absolutely solved most of the problem. In the late 2010s it was common for political accounts to use scripts that went through follower graphs for their worst repliers and blocked everyone, or went through the list of people liking a certain tweet and blocked all those accounts.

They were quite fond of that approach and were happy with the outcome pre-Elon. Even if someone in the "bad group" screenshotted a tweet from their target to make fun of it, the target didn't really get bothered by it because they walled themselves well enough. The screenshotter is incentivized to not interact with their target so they don't get blocked again, and no one excited by all the dunking cared enough to go harass the target anyway.

Now as someone who found themselves in a few blockchains during peak Bernie-mania, I like the proposed change. I've been blocked by several popular accounts because of who I followed, and I will enjoy being able to reliably read someone's content even if I'm not allowed to interact.

[pyuser583]

I enjoy your irregular use of the word “blockchain.”

[viraptor]

> Most X users will just post a screenshot of the tweet, breaking accessibility in the process and disassociating the original author from the thread against their will.

But that means the blocking worked. Another person will now have to go to the extra effort of either finding that tweet or going directly to the profile to interact with them. And those extra steps were exactly the feature the blocking provided. It changes "click reply, type 'kill yourself you <slur> <slur>'" into "login into non-blocked account, retype part of the text from the screenshot, search, find the matching tweet, reply, type". And that's a lot of work for a quick response.

Sure, it won't stop everyone. It reduces the effects though.

[miki123211]

You could design Twitter in a way where handles in quoted tweets aren't clickable if the quoter is blocked by the quotee, but the quotee can still be notified that they've been quoted by somebody they blocked, and optionally choose to see the post. Same for deletion, you could make quotes literally include the original post and preserve it forever, but notify viewers when the original is deleted.

[felipeerias]

> post a screenshot of the tweet, breaking accessibility in the process and disassociating the original author from the thread against their will.

I'm surprised that the platform does not do ORC on text images by default.

And it wouldn't be hard to check if a particular image looks like a tweet and, if it does, find out the exact match.