What you need to know
- Twitter is testing a new feature that lets you choose who can reply to the tweet you're composing.
- You'll have three permission options to choose from, including only the people you @mention.
- Others will still be able to view and like your tweets, but not reply.
Twitter has a problem with harassment and unwanted replies, and it's looking to alleviate that with a new feature it's testing that allows you to limit who's able to reply to your tweets. Initially rolling out to a small number of users globally, Twitter is adding a permissions option to the tweet composition screen, with three options to choose from.
The default setting will allow anyone to reply to your tweet, just as has always been the case on Twitter, but you can now choose to allow only the people you follow to reply, or even just the people you @mention in your tweet. This works on a per-tweet basis, rather than applying to all tweets on your profile.
A new way to have a convo with exactly who you want. We’re starting with a small % globally, so keep your 👀 out to see it in action. pic.twitter.com/pV53mvjAVTTesting, testing...
A new way to have a convo with exactly who you want. We’re starting with a small % globally, so keep your 👀 out to see it in action. pic.twitter.com/pV53mvjAVT— Twitter (@Twitter) May 20, 2020May 20, 2020
Users excluded from your permissions will still be able to view, like, and retweet your tweets, but they won't be able to respond. It's unclear whether users will be able to set their own permissions for their replies to your initial tweet at this time.
Hayato was a product reviewer and video editor for Android Central.
I can see this being abused by people with crappy takes on things or who spread disinformation/misinformation because they'll block replies so that people can't call them out on it.
True. There's a huge opportunity for misuse here.
Twitter testing out everything except an edit option.
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.