Hacker News new | past | comments | ask | show | jobs | submit login

> 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.






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.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: