I'm also having issues on not receiving new tweets when I use the
since_id value. Pretty much the same problem described in the above
comments.
I just wanted to make everyone aware that this issue is open and being
tracked [1]. Any progress or developments will be posted on that
thread.
If you are experiencing a problem with since_id I encourage you to
read my comment [2].
Thank you,
Matt
1. http://code.google.com/p/twitter-api/issues/d
Twitter, your "since_id" feature has been broken since October 2009,
and it is STILL broken. And yet you warn us that not using it will
result in blacklisting? Your search API is unreliable when since_id is
used. Someone at Twitter mistakenly closed the bug in December but oh
yes, it still exists,
Taylor:
Can we get clarification on the since_id issue? You have warned us
that not using since_id will get us blacklisted, and at the same time
since_id appears to still be broken according to others on this list.
Please advise.
What I do is request 100 responses per page, and then manually chec
Hi Taylor,
I've filed a bug report about using since_id with search 6 months ago
after my client users complained about empty / no search results:
http://bit.ly/since_id
Is this bug fixed already? If not, how can we use since_id with the
Search API so that it is giving us some results and not ju
Are you all aware of this bug?
http://code.google.com/p/twitter-api/issues/detail?id=1154
We can't reliably use since_id for searches until this is fixed.
On May 27, 6:12 pm, Taylor Singletary
wrote:
> Hi Developers,
>
> A few quick points before I go into more detail:
>
> * For the Search AP
