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

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
2 - friends/followers/lists all have a next_cursor, so does a search,
that works for me now.
3- Home timeline is an issue, but I can see how twitter will find that
difficult to count for me or give me a next_cursor, etc. I guess if
someone clicks 'more' once in a long while and I have to refresh to
the same page with no more button because my one extra read showed no
more updates, then I can live with that.

Unless someone has a better idea?


On Aug 11, 11:33 am, Tom van der Woerdt <> wrote:
> 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.
> Tom
> On 8/11/10 5:30 PM, Mark Krieger wrote:
> > 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 always really send me back 20 results
> >>> ALWAYS, then if less, I know this is the last screen.
> >> Unfortunately, that won't work. Twitter retrieves the messages from
> >> the cache and then tests if they still exist. This means you could
> >> receive less than 20 and still not being in the last page.
> >> --
> >> Julio Biason <>
> >> Twitter:

Reply via email to