Hello!
We regularly fetch feeds from the Twitter API and then take the max id
as the sinceid to subsequent calls.
The problem is that in the last two days, we suddenly are getting lots
of
"Couldn't find Status with ID=XYZ"
messages. We weren't seeing these before, but now multiple times a
day
We've started seeing this too. If we specify a since_id, then
periodic refetches will frequently return "no new tweets" (but
sometimes they will return new ones).If we simply drop the
since_id, then all new tweets are fetched.
Some new server optimization thing gone wrong?
Thanks!
On Oct
Hello Damon!
I'm not 100% sure I buy this explanation:
1. This problem wasn't happening a day or two ago.
2. I tried executing the query on the command line, and incremented
the since_id by 1 maybe 8-10x ... it just doesn't return any results.
Even weirder is that if I wait 20 minutes, and exe
A number of people are seeing similar things, especially if you
specify a since_id:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e6289b6439c1d26d/e367ca8af09d28d5?lnk=gst&q=searches+returning+no+tweets&pli=1
My current (extremely bad) solution is to just "hire ho
h.json?q=hong+kong+OR+kowloon+OR+tsim+tsa+shui&rpp=100
and then the results STOP coming if there is a since_id
I've filed a support ticket with Twitter ( 623447 ) with this info,
and hopefully we'll see some progress on it.
Mark.
On Oct 28, 9:56 am, Marc W wrote:
>
