You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.
Allow user to incrementally explore more tweets beyond the current 1000-tweet limit, eg with a ‘More’ button that is enabled when allowed by Twitter’s rate limit. For this to work, we need to ensure that the results are returned in chronological order. Two approaches are, in order of priority:
(1) One button to search further in the past would simply continue the current "cursor"/pagination, when the Twitter API allows it.
(2) Another button to run the query again, merging the previous results with those in the intervening time interval, say, 15 minute later.
The text was updated successfully, but these errors were encountered:
Allow user to incrementally explore more tweets beyond the current 1000-tweet limit, eg with a ‘More’ button that is enabled when allowed by Twitter’s rate limit. For this to work, we need to ensure that the results are returned in chronological order. Two approaches are, in order of priority:
(1) One button to search further in the past would simply continue the current "cursor"/pagination, when the Twitter API allows it.
(2) Another button to run the query again, merging the previous results with those in the intervening time interval, say, 15 minute later.
The text was updated successfully, but these errors were encountered: