You can pull the most recent 3200 statuses for a user and that is it.
Abraham
On Tue, Aug 4, 2009 at 00:24, Dharmesh Parikh dharmesh.par...@gmail.comwrote:
So if i user_timeline REST api call and use max_id =X or since_id = Y and
count=200 i can get 3200 messages backwards from X or 3200
Hi there --
Check out #6 in the Things Every Developer Should Know article [1].
1. https://apiwiki.twitter.com/Things-Every-Developer-Should-Know
Thanks,
Doug
On Sun, Aug 2, 2009 at 11:27 AM, dp dharmesh.par...@gmail.com wrote:
When the REST API limit for using count/page reaches 3200 for a
Hi Doug,
I did read that but was not able to get the exact implications of it,
thats why the question.
So lets say i use count to get 3200 messages in history for a user,
then can i use the count ever again (count 20), or i have reached the
limit for that user permanently??
-dharmesh
On Aug
I believe it means you can not go back more than 3200 statuses.
Example:
user has posted 5000 statuses. you can only view statuses 3200+ via the
api.
Its not a limit that gets used up like the api rate limit.
On Mon, Aug 3, 2009 at 1:39 PM, dp dharmesh.par...@gmail.com wrote:
Hi Doug,
I
Correction: 3200--1800
Sorry for that math error ;)
On Mon, Aug 3, 2009 at 2:03 PM, Josh Roesslein jroessl...@gmail.com wrote:
I believe it means you can not go back more than 3200 statuses.
Example:
user has posted 5000 statuses. you can only view statuses 3200+ via the
api.
Its not a
So if i user_timeline REST api call and use max_id =X or since_id = Y and
count=200 i can get 3200 messages backwards from X or 3200 messages forward
from Y and then hit the limit.
My specific questions:
1) can i use some different max_id and count=200 after the above scenario is
hit.
2) What
