I'm *not* using since_id, but I'm sporadically getting warning
messages about it. Most of the time, my queries work.
d:\curl http://search.twitter.com/search.json?q=
%23jquerylang=enpage=1show_user=truerpp=15
{
results: [{
profile_image_url: http://a1.twimg.com/profile_images/353780044/
I am seeing issues with twitter search using since_id.
The search results the query returns is not correct for atleast few
hours. I think, some synchronization happens every certain number of
hours. Also, if since_id is old, it expires.
I don't find it to be that useful.
Thanks,
Arjun.
The
We are experiencing the same thing as Marc. We are not using from:
though.
But intermittently it gets tweets in significant number. If I try to
get the same set again using the since_id for this particular crawl, I
again get no tweets.
Any Idea on this issue?
Thanks.
On Oct 23, 10:48 am, Marc
Christopher
To my recollection, for search with since_id to work properly, the
tweet id must be in the search index. In this case:
http://search.twitter.com/search?q=+from%3Asilent_tester02
does not yield the Dinner, movie, drinks. tweet in the index.
As an aside, I did an exact match search
I'm getting the same issue as Marc and harshavs too.
I'm using since_id to start a search from the last set of resuts but
generally get 0 results most of the time, even though the same search
without since_id yields lots of results.
I could start logging tweet IDs against user IDs, and then
