[twitter-dev] getting historical data for more than 150 / 300 users
How can an app get the historical twitter stream for more than 150 / 300 users in an hour? Those users are all signing up to our service and giving us their Oauth tokens. If more than 150 / 300 sign up in an hour, we can't get their historical data using the REST API because of Twitter's limits. Twitter's streaming API will let us get tweets for that user going forward in time, but won't allow us to see the tweets that are already in their stream. Is there any solution for this use case? We want to offer a service that parses user's twitter streams for statistical data, but if we can't go back and get their historical record, they'll have nothing when they first log in to the site. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
RE: [twitter-dev] getting historical data for more than 150 / 300 users
If you use their OAuth token for each request, then aren't you counting against their usage limit? You could have 5000 users sign up in an hour. You perform 5000 API calls using 5000 different OAuth tokens. Each API call is one count against each token. Each user now has one less API call left that hour. That's how I understand it ... -- Tatham Oddie If you're printing this email, you're doing it wrong. This is a computer, not a typewriter. -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of fifi Sent: Tuesday, 29 March 2011 9:42 AM To: Twitter Development Talk Subject: [twitter-dev] getting historical data for more than 150 / 300 users How can an app get the historical twitter stream for more than 150 / 300 users in an hour? Those users are all signing up to our service and giving us their Oauth tokens. If more than 150 / 300 sign up in an hour, we can't get their historical data using the REST API because of Twitter's limits. Twitter's streaming API will let us get tweets for that user going forward in time, but won't allow us to see the tweets that are already in their stream. Is there any solution for this use case? We want to offer a service that parses user's twitter streams for statistical data, but if we can't go back and get their historical record, they'll have nothing when they first log in to the site. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] getting historical data for more than 150 / 300 users
As Tatham said, each access token gives you up to 350 GET Request per hours. Make some requests (signing them with different access tokens) and look at the X-RateLimit-Remaining header. Arnaud / @rno On Mon, Mar 28, 2011 at 6:29 PM, Tatham Oddie tat...@oddie.com.au wrote: If you use their OAuth token for each request, then aren't you counting against their usage limit? You could have 5000 users sign up in an hour. You perform 5000 API calls using 5000 different OAuth tokens. Each API call is one count against each token. Each user now has one less API call left that hour. That's how I understand it ... -- Tatham Oddie If you're printing this email, you're doing it wrong. This is a computer, not a typewriter. -Original Message- From: twitter-development-talk@googlegroups.com [mailto: twitter-development-talk@googlegroups.com] On Behalf Of fifi Sent: Tuesday, 29 March 2011 9:42 AM To: Twitter Development Talk Subject: [twitter-dev] getting historical data for more than 150 / 300 users How can an app get the historical twitter stream for more than 150 / 300 users in an hour? Those users are all signing up to our service and giving us their Oauth tokens. If more than 150 / 300 sign up in an hour, we can't get their historical data using the REST API because of Twitter's limits. Twitter's streaming API will let us get tweets for that user going forward in time, but won't allow us to see the tweets that are already in their stream. Is there any solution for this use case? We want to offer a service that parses user's twitter streams for statistical data, but if we can't go back and get their historical record, they'll have nothing when they first log in to the site. -- Twitter developer documentation and resources: http://dev.twitter.com/docAPI updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
