[twitter-dev] Search API problems...

2010-08-24 Thread Ben
Hey guys -

I'm curious as to know whether there's any problems with the search
API?

I'm curling from a PHP script, and it keeps timing out with 'couldn't
connect to host' errors when my URL is a search (eg:
http://search.twitter.com/search.atom?q=test). Interestingly, if I
curl either of the following:

http://api.twitter.com/1/help/test.xml
http://api.twitter.com/1/account/rate_limit_status.xml

...and it doesn't time out, I get a true, and my rate limit is
150/150. I'm not using any authentication, this is a straight request
from a script.

Could I be on an IP blacklist for search (can I check this?)? I've
been pretty careful with my caching, I make nowhere near 150 requests
an hour, although my site is on a shared server, so it's entirely
plausible someone else has been hammering it. Although if that was the
case, would something not show up on the odd times I actually get the
rate limit to show something?

If anyone can help, or point me in the direction of something I've
missed, I'd be eternally grateful...


ben

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en


Re: [twitter-dev] Search API problems...

2010-08-24 Thread Matt Harris
There are no known issues with search and running your query works for me.
Hey Ben,

The Search API does not use authentication and is rate limited
differently to the 150 IP requests allowed on the REST API.
If you are rate limited on the Search API we would return an error
telling you rather than not reply.

If the atom link is still not responding can you try
http://search.twitter.com/search.json?q=test and let us know the
result?

Thanks,
Matt



On Tue, Aug 24, 2010 at 4:28 PM, Ben  wrote:
> Hey guys -
>
> I'm curious as to know whether there's any problems with the search
> API?
>
> I'm curling from a PHP script, and it keeps timing out with 'couldn't
> connect to host' errors when my URL is a search (eg:
> http://search.twitter.com/search.atom?q=test). Interestingly, if I
> curl either of the following:
>
> http://api.twitter.com/1/help/test.xml
> http://api.twitter.com/1/account/rate_limit_status.xml
>
> ...and it doesn't time out, I get a true, and my rate limit is
> 150/150. I'm not using any authentication, this is a straight request
> from a script.
>
> Could I be on an IP blacklist for search (can I check this?)? I've
> been pretty careful with my caching, I make nowhere near 150 requests
> an hour, although my site is on a shared server, so it's entirely
> plausible someone else has been hammering it. Although if that was the
> case, would something not show up on the odd times I actually get the
> rate limit to show something?
>
> If anyone can help, or point me in the direction of something I've
> missed, I'd be eternally grateful...
>
>
> ben
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk?hl=en
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en