Same thing here, it started to happen since yesterday. When doing
searches with parameter from:username and since_id, sometimes I got
the tweet with since_id back as well.
It only happens some times, not every time, so I suspect it's a bug
other than API change. Any idea?
On Sep 23, 9:40 am,
Thanks for reporting this. If there is a way for you to capture
request/response logs when this happens it will help our search team
to track this down. Since it is happening inconsistently it may mean
that one of the servers is acting funny, and the HTTP headers could
help track that down.
