Twitter will now publicly flag offensive tweets

They will be replaced with a post reading "This tweet is no longer available because it violated the Twitter Rules"


Tech Desk October 18, 2018
The shadows of people holding mobile phones are cast onto a backdrop projected with the Twitter logo in this illustration picture taken in Warsaw September 27, 2013. Twitter Inc, the eight-year-old online messaging service, gave potential investors their first glance at its financials on Thursday when it publicly filed its IPO documents, setting the stage for one of the most-anticipated debuts in over a year. Picture taken September 27. PHOTO: REUTERS

Public exposure certainly helps deter unwanted behaviour. Twitter is taking this pretty seriously after cracking down on users who violate the social media giant’s terms of service.

On Wednesday, the company announced that any such tweets will be replaced with a post reading "This tweet is no longer available because it violated the Twitter Rules."

Twitter sets crackdown on automated 'bot' accounts

It will remain up for 14 days after the user deletes the offending Tweet. Anyone visiting the profile would know that the user posted a message that someone else successfully reported.



Tweets will also look a bit different for people who reported a tweet. If they come across a tweet they've previously reported, in place of the offending tweet, users will see a warning that would say "You reported this tweet."



The company already has a restriction in place that requires users to delete a tweet that has violated Twitter's terms of service before being able to tweet again. This new initiative just makes that action more visible to everyone.

Twitter to ban 'dehumanising' comments with user help

It's a simple example of how public shaming can alter unwanted behaviour and the social media giant is wasting no time in putting the technique to good use.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ