【sex video with leicester city players】

Did you know that when someone blocks you on sex video with leicester city playersX (formerly Twitter), they can still reply to your posts? This opens up the possibility of abuse, with someone blocking you and then slandering, impersonating, or otherwise abusing you on the very same platform without you seeing it.

Now, X is changing the way blocking works. On Thursday, the company's Engineering account explained the changes as follows: "If a user who has blocked you replies to one of your posts, you will now be able to see their reply. This change enables you to identify and report any potential bad content that you previously could not view, safeguarding both your account and the overall integrity of our platform."

This Tweet is currently unavailable. It might be loading or has been removed.

X owner Elon Musk previously said the block functionality on X "makes no sense," and that it's going to be "deleted as a 'feature' except for DMs." While that hasn't happened yet, it appears that X is working towards changing the block feature until it's more in line with Musk's idea of the platform functioning as a "public town square."

"Our goal is to allow users to control their experience while maintaining the public visibility of posts," the post from X's Engineering team added.

• Stephen King trolls Elon Musk once again over Twitter's name change
• We're all crumpled up pieces of paper lying here as Twitter reacts to 'Red (Taylor's Version)'
• Look what you made them do: People can't stop tweeting about Taylor Swift, Twitter confirms
• Twitter/X staff ignored Elon Musk's orders, prevented an FTC violation
• Twitter/X might charge all new users a 'small fee' before they can post, like, and reply

An unresolved issue remains: Reporting abuse on X doesn't seem to do much. I've reported numerous scam accounts over the past couple of months, and they seem to just keep on appearing. The company's strategy of charging users for the "verified" blue checkmark hasn't done much to fix the problem, either.

(Editor: {typename type="name"/})