Hide replies v2 (deprecated)

Please note:

We recently graduated hide replies into Twitter API v2: Early Access and announced a 90-day deprecation window. We will retire this endpoint in November 2020.

Learn more about the new hide replies endpoint, and review our migration resources to update to the new Twitter API.

 

Getting started with the hide replies endpoint

This guide will help you understand how your app can help people hide replies.

Before you can start, you will need the following:

 

Authentication

Your app will be hiding replies on behalf of the author of the original Tweet. For this reason, requests must use OAuth 1.0a (also known as user-context authorization). This means that you must use the API key and secret of your Twitter developer app, as well as the Tweet owner's access token and access token secret to make a request to the endpoint. If you need to generate an access token and secret for the Tweet owner, you can do so with the 3-legged OAuth process.
 

Help users hide replies

Your app should consider various approaches to using the hide replies API, including suggesting replies to hide for your users; or automatically hiding replies that have a very high probability of being irrelevant for your users.

Useful apps often combine technologies so that they can be valuable to their users. The following example shows how to hide replies by using the Perspective API. This API is an artificial intelligence trained by Jigsaw, a unit within Google, to detect toxic comments. The application logic will work in the following way:

  1. It asks the user’s permission to read their Tweets and hide their replies.
  2. It uses the Account Activity API to detect incoming replies.
  3. It asks the Perspective API to give a “score” (a number between 0 and 1) that indicates how confident their algorithm is that a comment is similar to toxic comments it’s seen in the past. (Perspective does not store the text sent to the service).
  4. It calls Hide replies if the algorithm’s score is very high.
     

Strive for transparency

Because Perspective is not trained on actual Tweets, certain language nuances may cause this app to hide a reply that a user wants to remain unhidden. Regardless of the technology or the approach you use when designing your app, always make the best possible effort to ensure that your users understand what your app has hidden and can make changes.

  • The best option is to always trust the user and to give them full control over their decisions. When this is not desirable, your app should use a very high confidence threshold to detect and hide Tweets.
  • Not everybody uses the same words, and your app should be designed to avoid any bias. Be mindful of reclaimed words and slang that may lead to false positives.
  • If you are training an artificial intelligence, consider adopting a model that closely reflects language often used on Twitter.

 

 


 

Additional resources

  • Check out our API reference to learn more about what’s available. 
  • Learn more about the new Developer Labs on the "About Labs" page. 
  • Give feedback on Twitter Developer Labs. 
  • Tell us about your experience using the Twitter Developer Labs endpoints by filling out this survey.

Was this document helpful?

Thank you

Thank you for the feedback. We’re really glad we could help!

Thank you for the feedback. How could we improve this document?

Thank you for the feedback. Your comments will help us improve our documents in the future.