Twitter Developer Feedback

Twitter Developer Labs

We want to hear your ideas for Twitter Developer Labs! How would you improve the current available endpoints in Labs, and what other things would you like us to consider building?

1. See what other ideas have been submitted and vote for ideas you like.
2. If you have an idea that isn't already listed, create a new post.
3. Include only one idea per post.

To start, we have added in a few ideas that have been suggested by developers in the past. Please vote or comment on those, if they reflect your own vision.

Thank you for participating!

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. API to report abuse/inappropriate content

    I suggest that the report features extend to API users. Report abuse is only available for individuals who get exposed to, click, and decide to report a tweet/account.

    A lot of inappropriate content is unfortunately on twitter. Perhaps I could categorize into 4 types:
    (1) inappropriate language: hate speech, harassment (bullying, sexual harassment)
    (2) inappropriate image: pornography, graphic violence
    (3) intention for inappropriate and harmful activities: intention to commit a crime (shooting, bomb, individual or mass threats), sell inappropriate products and services (prostitution, drugs - not debating if it is illegal or not, but I think twitter shouldn't be the…

    40 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  7 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Build an API to create and retrieve Tweet threads

    Tweet threads have become increasingly popular over the past few years. This API would enable developers to tap into the potential of threads by programmatically creating threads, as well as retrieving all Tweets in a thread.

    45 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  5 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Hide Replies and Block Users should be combined in a wiser way

    Currently, there is an easy way troll farms already circumvent the "hide replies" feature:
    1) post a disinfo/harrassmt reply to a target account
    2) then immediately block (blacklist) the target account
    3) now the abusing reply is visible for everyone, but neither attacked account nor anyone else can do anything with it.

    I don't have a solution that will surely fix this. I understand that this is actually feedback on how Hide Replies works for users, not how it should be available via API. Any better place to post feedback on user feature and to be sure it will be

    3 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Daniele responded

    Thank you for this feedback, and appreciate the level of detail. Your voice is heard here – We’re passing this to the team working on Hide replies for users so they can review.

  4. Show when a Tweet is hidden in the Tweet payload

    The Tweet payload should contain a field that indicates whether a Tweet has been hidden. This can help people maintain display consistency regardless of where they manage their Twitter accounts. Researchers can find the field useful to understand circumstances such as relevancy, confusion and abuse.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow to serve 10Ks-100Ks of users subscribed for a HideReplies app

    Allow a free-plan developer to serve 10Ks-100Ks of users subscribed for a "hide replies" allowing to hide tweets nearly real-time as they happen (provided that an app is capable to deal with such a firehose).

    This at least requires easy access to a stream of direct and indirect replies to the users subscribed.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
  6. Proximity operator

    From the operator reference [0], the filtered streams appear to lack the proximity operator, that existed in Gnip PowerTrack.

    Having this in the filtered stream API would make it easier to migrate from Gnip.

    Additionally, in PowerTrack the maximum proximity value is 6. Increasing this limit would make the operator extra useful.

    [0] https://developer.twitter.com/en/docs/labs/filtered-stream/operators

    1 vote
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base