Same here; my app runs on Google App Engine and 40% of the requests to the Twitter Search API get the 503 error message indicating rate limiting.
Is there anything we as app authors can do on our side to alleviate the problem? /Martin On Oct 5, 1:53 pm, Paul Kinlan <paul.kin...@gmail.com> wrote: > I am pretty sure there are custom headers on the App Engine that indicate > the application that is sending the request. > > 2009/10/5 elkelk <danielshaneup...@gmail.com> > > > > > > > Hi all, > > > I am having the same issue. I have tried setting a custom user-agent, > > but this doesn't seem to affect the fact that twitter is limiting > > based on I.P. address. I'm only making about 5 searches an hour and > > 80% of them are failing on app engine due to a 503 rate limit. > > Twitter needs to determine a better way to let cloud clients access > > their search API. It seems like they have really started blocking > > search requests in the last week or so. > > > If anyone has any idea about how to better identify my app engine app > > please let let me know. > > > On Oct 5, 2:59 am, steel <steel...@gmail.com> wrote: > > > Hi. I have this problem too. > > > My application does two request per hour and it get "rate limit". > > > What is wrong? I think it is twitter's problems.... > > > > On 1 окт, 01:45, Paul Kinlan <paul.kin...@gmail.com> wrote: > > > > > Hi Guys, > > > > I have an app on the App engine using the search API and it is getting > > > > heavily rate limited again this past couple of days. > > > > > I know that we are on a shared set of IP addresses and someone else > > could be > > > > hammering the system, but it seems to run for weeks without seeing the > > rate > > > > limit being hit and then all of a sudden only about 60% of the searches > > > > I perform will be rate limited. This seems to occur every two months > > or so. > > > > > Has something changed recently? > > > > > Paul
