Same issue here. Mobile app does local caching and was counting on the
since_id not being included in the result set. Unfortunately, I
haven't been capturing request and response logs.
On Sep 23, 9:40 am, James Teters <jtet...@gmail.com> wrote:
> This has just appeared in the last few days. When I perform a search
> with the search API I keep track of the newest status id so I can pass
> that back when doing the next query (as since_id) so that only tweets
> with a status id greater than since_id are returned. Oddly, beginning
> yesterday the search API started returning the status specified in
> since_id but only when I specify a from: parameter to limit the search
> to a specific user. It's like it is returning statuses >= since_id
> instead of > since_id when I add the from: parameter.
> Anyone else seen odd behavior when using from:?