Re: [twitter-dev] collecting tweet message ids
Hi Matt, thanks for clearing up my questions! -- Kind Regards, Rajinder Yadav On 10-11-29 05:09 PM, Matt Harris wrote: Hi Rajinder, We would really like to offer access to the historical timeline but our infrastructure doesn't allow access to anymore than 3200 right now. The Tweets are safe and have not been deleted or lost, they are just not available. We also don't have a timeline for access to historical tweets right now. In answer to your second question, when there are no more statuses available we'll return an HTTP 200 with an empty timeline. For example: JSON: [] XML: ?xml version=1.0 encoding=UTF-8? statuses type=array /statuses Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Nov 29, 2010 at 10:42 AM, Rajinder Yadav devguy.ca http://devguy.ca@gmail.com http://gmail.com wrote: On Mon, Nov 29, 2010 at 12:27 PM, Matt Harris thematthar...@twitter.com mailto:thematthar...@twitter.com wrote: Hi Rajinder. The user_timeline returns upto 200 statuses per page starting with the most recent. To retrieve a complete page of 200 you will want to make a request similar to: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1 http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1 This request will return upto the most recent 200 statuses. To retrieve the next 200 you would make this request: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1\page=2 http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1\page=2 When requesting this many statuses at once you may get a 503 error response from us. If this happens wait a few seconds and try the request again. Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris Hi Matt, thanks, that is a better solution than what I have been using. Questions, am I limited up to only 3200 statuses? is it possible to go beyond this limit and get the entire statues for a user? When there are no more status request (empty set), what http error code can I expect. Likewise if 3200 status is a hard limit what http error will I get when this limit is hit? Finally if I have exceeded my rate limit what is the http code returned? Kind Regards, Rajinder Yadav -- 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] collecting tweet message ids
Hi Rajinder. The user_timeline returns upto 200 statuses per page starting with the most recent. To retrieve a complete page of 200 you will want to make a request similar to: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1 This request will return upto the most recent 200 statuses. To retrieve the next 200 you would make this request: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1\page=2 When requesting this many statuses at once you may get a 503 error response from us. If this happens wait a few seconds and try the request again. Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Nov 25, 2010 at 9:07 PM, Rajinder Yadav devguy...@gmail.com wrote: Hi I would like to know how I can go about retrieving all the tweet message ids from a user's timeline? I am using the user_timeline to get the message ids, is there a better faster way? The following page seems to indicate I can obtain up to 3200 statuses. http://dev.twitter.com/doc/get/statuses/user_timeline However I am not able to fetch 3200 statuses. Also if I pass in a count of 200, I something only get 20 in my result other times 4, this occurs in the cases where there are say 4 statuses by the user. If I have to make multiple calls, how can I go about fetching a list of all the user_timeline message ids? Also can someone from please explain to me how the page parameter works, specially in the case of varying result sizes? Finally how is the message ordered in the user_timeline, can I make an assumption that the last status at the bottom on the page will always be older than the top? Thanks, -- Kind Regards, Rajinder Yadav -- 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] collecting tweet message ids
On Mon, Nov 29, 2010 at 12:27 PM, Matt Harris thematthar...@twitter.com wrote: Hi Rajinder. The user_timeline returns upto 200 statuses per page starting with the most recent. To retrieve a complete page of 200 you will want to make a request similar to: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1 This request will return upto the most recent 200 statuses. To retrieve the next 200 you would make this request: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1\page=2 When requesting this many statuses at once you may get a 503 error response from us. If this happens wait a few seconds and try the request again. Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris Hi Matt, thanks, that is a better solution than what I have been using. Questions, am I limited up to only 3200 statuses? is it possible to go beyond this limit and get the entire statues for a user? When there are no more status request (empty set), what http error code can I expect. Likewise if 3200 status is a hard limit what http error will I get when this limit is hit? Finally if I have exceeded my rate limit what is the http code returned? Kind Regards, Rajinder Yadav -- 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] collecting tweet message ids
Hi Rajinder, We would really like to offer access to the historical timeline but our infrastructure doesn't allow access to anymore than 3200 right now. The Tweets are safe and have not been deleted or lost, they are just not available. We also don't have a timeline for access to historical tweets right now. In answer to your second question, when there are no more statuses available we'll return an HTTP 200 with an empty timeline. For example: JSON: [] XML: ?xml version=1.0 encoding=UTF-8? statuses type=array /statuses Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Nov 29, 2010 at 10:42 AM, Rajinder Yadav devguy...@gmail.comwrote: On Mon, Nov 29, 2010 at 12:27 PM, Matt Harris thematthar...@twitter.com wrote: Hi Rajinder. The user_timeline returns upto 200 statuses per page starting with the most recent. To retrieve a complete page of 200 you will want to make a request similar to: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1 This request will return upto the most recent 200 statuses. To retrieve the next 200 you would make this request: http://api.twitter.com/1/statuses/user_timeline.json?count=200\include_rts=1\page=2 When requesting this many statuses at once you may get a 503 error response from us. If this happens wait a few seconds and try the request again. Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris Hi Matt, thanks, that is a better solution than what I have been using. Questions, am I limited up to only 3200 statuses? is it possible to go beyond this limit and get the entire statues for a user? When there are no more status request (empty set), what http error code can I expect. Likewise if 3200 status is a hard limit what http error will I get when this limit is hit? Finally if I have exceeded my rate limit what is the http code returned? Kind Regards, Rajinder Yadav -- 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] collecting tweet message ids
next_cursor_str it's paginated. On Nov 26, 2010, at 12:07 AM, Rajinder Yadav wrote: Hi I would like to know how I can go about retrieving all the tweet message ids from a user's timeline? I am using the user_timeline to get the message ids, is there a better faster way? The following page seems to indicate I can obtain up to 3200 statuses. http://dev.twitter.com/doc/get/statuses/user_timeline However I am not able to fetch 3200 statuses. Also if I pass in a count of 200, I something only get 20 in my result other times 4, this occurs in the cases where there are say 4 statuses by the user. If I have to make multiple calls, how can I go about fetching a list of all the user_timeline message ids? Also can someone from please explain to me how the page parameter works, specially in the case of varying result sizes? Finally how is the message ordered in the user_timeline, can I make an assumption that the last status at the bottom on the page will always be older than the top? Thanks, -- Kind Regards, Rajinder Yadav -- 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 Regards, Edward Hotchkiss edw...@edwardhotchkiss.com http://www.edwardhotchkiss.com/ -- 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
