I've had the same problem...I thought I was jumping over a rate limit
from my location, but I'd like to hear from someone on Twitter on
this. I'm getting ready to launch a website with a Twitter search on
the homepage, and I don't want a "no results" message coming up due to
error failover in my code.

On Jan 12, 2:44 pm, whozman <tweet...@gmail.com> wrote:
> It does not matter what I search for. The json and atom responses are
> not coming back either.
> I believe that this is some kind of routing problem because when I log
> onto a server in US and do the same it works (I do my queries normally
> from Canada). To test, it is quite easy, just do any query on
> search.twitter.com directly such as:http://search.twitter.com/search?q=twitter
> from an IP that is in Canada. I think it happens elsewhere in the
> world based on some tweets that I have seen while searching for
> search.twitter.com.
> The search on main twitter site is unaffected 
> (i.e.http://twitter.com/#search?q=twitter
> works) as it uses some different mechanism (what is that mechanism,
> that would be nice to know, because I certainly would like to have the
> same level of reliability as the main site at least, I don't think
> that streaming api is the solution as it requires authentication).

Reply via email to