Twitter Developer Feedback

Digital Observatory Team

My feedback

  1. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  4 comments  ·  Twitter for Academic Research » APIs & Tools  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Digital Observatory Team commented  · 

    Main differences from the existing functionality:

    - Higher rate limit enabled by much smaller payload. Why retrieve the raw JSON again for a tweet to check if it's live, when my only interest is the immutable field like tweet content?

    Although the lookup API can do this (and a higher rate limit would ease this process), it's challenging to build a good pipeline around this. Most use cases of tweet data are going to require processing the raw JSON into some other more useful schema.

    I don't see this as a replacement for statuses/lookup in terms of compliance, more an adjunct that allows a more rapid response and the ability to more frequently keep a collection in sync with live Twitter.

    Digital Observatory Team shared this idea  · 
  2. 30 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Digital Observatory Team supported this idea  · 
  3. 57 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Twitter for Academic Research » APIs & Tools  ·  Flag idea as inappropriate…  ·  Admin →
    Digital Observatory Team supported this idea  · 

Feedback and Knowledge Base