Thanks for the suggestion. I think I probably have a good but not
perfect solution which is much less work and also not likely to ever
fail:
1 - favorites and specific user updates have a count associated with
them at any time. I can use that count to know when I am done. Pretty
much.
2 - friends/
You could simply request twice as many as you need and do the math.
However, in rare occasions (very rare) it could happen that an user sent
20 tweets and deleted all of them, in which case it may look like you
are at the end of the list.
It is not recommended to use two API calls for 20 messages.
Thanks for the quick response, that is what I thought I had
remembered.
Does this mean that I always need to read-ahead to see if I am on the
last page?
Mark
On Aug 11, 10:48 am, Julio Biason wrote:
> On Wed, Aug 11, 2010 at 8:43 AM, Mark Krieger wrote:
> > 2. Assume that these calls will alwa
