Hi,  we've been receiving lots of Twitter/timeout errors on search
with 502 error codes.  The account we use is "klout". I would say 1 in
4 calls to search result in 502s...  Any ideas on how to reduce the
errors?  Maybe go 50 instead of 100 results?

example call:

http://search.twitter.com/search.atom?q=&from=username&phrase=bit.ly&rpp=100&page=1

Reply via email to