I noticed the same behavior in my app: when I include since_id in the
search API call, I often don't get all the tweets I should. If I run
without since_id, I see tweets with IDs that should have shown up in
the search where I included since_id.

Any response from Twitter? The since_id parameter is a very useful
feature of the API. It would reduce system load and bandwidth
considerably for everyone if it worked right.


On Nov 23, 6:14 pm, Hayes Davis <ha...@appozite.com> wrote:
> +1 on this. I'm frequently getting 0 results from the search API (not an
> error, just 0 results) when including the since_id even though a search
> without the since_id shows that there are tweets with larger ids for the
> same query string.
> Hayes
> On Mon, Nov 23, 2009 at 1:16 AM, Karthik <fermis...@gmail.com> wrote:
> > I have this problem as well. I use "since_id" and I query for newer
> > results every minute. For past 10 days, I'm seeing my app was not
> > indexing many tweets. I compared the results with search.twitter.com
> > and I can clearly see that I'm missing out a lot of tweets, if I keep
> > including the since_id parameter. I guess, there are some issues in
> > the search system.
> > On Nov 19, 3:30 am, Tadeu Andrade <tadeu.andr...@gmail.com> wrote:
> > > hi folks,
> > > since last week, I noticed thatsearchis behaving a little strange.
> > > For example, if I do a query on a keyword using since_id, sometimes I
> > > get no results. If I remove since_id parameters, the query succeed and
> > > if I repeat the initial query (with since_id), then I get results.
> > > Same thing occurs if I query from the web page and later from API (via
> > > json).
> > > Anyone else has noticed this weird behavior?
> > > cheers
> > > Tadeu

Reply via email to