Searched the bug database again and found that someone had reported
this a couple of weeks ago:
http://code.google.com/p/twitter-api/issues/detail?id=1154
I added my experience with the bug to the existing bug report and
starred it. If you care about since_id working in searches, feel free
to
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
On Sun, Dec 6, 2009 at 3:24 PM, Martin Omander moman...@google.com wrote:
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
+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
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
