Hello Chad, Can you confirm that this is not the case for AWS elastic IPs which had been previously whitelisted by Twitter?
Thanks, Darren On Aug 21, 4:35 pm, Chad Etzel <[email protected]> wrote: > Hello, > > I have replied to Jud off-list, but for everyone's benefit we'd like > to reiterate that AWS and GAE are shared resources and therefore share > the rate limit across applications. A dedicated IP and unique UA will > guarantee the maximum API limits. There are several cheap and reliable > VPS hosting services available which can provide a dedicated IP > address and full control over the server. > > Thanks, > -Chad > > On Fri, Aug 21, 2009 at 12:48 PM, Jud<[email protected]> wrote: > > > I've got a python app running on Google App Engine (appspot hosted) > > that querieshttp://search.twitter.com/search.atom?q=for simple > > queries (e.g. "foo OR bar"), and it's being severely throttled (e.g. > > can't get a successful request through (response 200 w/ data) more > > than a couple of times per _hour_). > > > - I'm setting the UA string to something unique/identifiable (e.g. my > > company name) > > - I'm respecting the retry-after header coming back when I see a 503 > > (average retry-after duration is ~750) > > - GAE turns the IP address behind the app over ~ every 6 hours > > - app hits tries to hit search.twitter.com every 5 minutes. > > > I've successfully polled the endpoint at much higher rates (in > > completely different IP address ranges) in the past, without issue. > > Unclear what's going on. Any suggestions would be greatly appreciated.
