-----Original Message-----
From: Trevor Turk <trevort...@gmail.com>

Date: Sun, 30 Nov 2008 23:16:14
To: Twitter Development Talk<twitter-development-talk@googlegroups.com>
Subject: since_id limit

I'm just reviewing the API docs, and I'm not clear on something.

http://apiwiki.twitter.com/REST+API+Documentation#replies

If you pass in a since_id, then do you get ALL the results since that
ID, or just the latest 20?

I'm planning to ping Twitter every minute and collect the @replies
sent to a particular user. I'm sure I won't get more than 20 @replies
per minute, but I would like to know if that's something I should note
for the future.

Thanks,
- Trevor

> If there are more than 20 results, you can use paging to grab them all.

> But didn't the since_id parameter return all tweets since that ID
> originally? I have a Twitter client that I've coded which was working
> fine with since_id till yesterday (December 1st). But since yesterday
> it only returns the last 20 tweets. Was a functionality/API change
> made?

> On Dec 1, 6:38 pm, "Brian Gilham" <bgil...@gmail.com> wrote:

> > If there are more than 20 results, you can use paging to grab them all.

> Kind regards,

> Fahim

> There was a small change. They fixed a bug with since_id where it
> would set it as 0 if the status had been deleted (#77). It looks like
> they now require a count parameter as well.

> On Dec 3, 11:39 am, Swap <RH.Swar...@gmail.com> wrote:

> > There was a small change. They fixed a bug with since_id where it
> > would set it as 0 if the status had been deleted (#77). It looks like
> > they now require a count parameter as well.

> So what's a good workaround? Request the next page if you get 20
> results? Too bad, but still doable :)

> - Trevor