I cooled down my servers for more than 2 hours now. There were no activities happening through my app. I turned it back on just a few minutes back.
The same problem, getting 420 error codes :( Cooling it off again, can you do something to get me out of this trouble? -N On Apr 6, 9:07 pm, nischalshetty <[email protected]> wrote: > Though I have so many users, each user has an internal limit of 100 > unfollows per day which is well within any sort of limits. That is one > of the reasons why I never implemented any queuing mechanism, such > short number of unfollows can be done instantly. > > Besides, there were no sudden spikes in traffic so this sudden rate > limiting baffles me. And automated unfollows are not allowed so I > thought queuing wouldn't be a good idea. I'll try to implement > something like that but what's the short term solution? Can you do > something on your end to remove the rate limit if any that might have > been put on my app? > > I have always adhered to twitter limits and rules never going out of > my way. Please help me with this. > > -Nischal > > On Apr 6, 9:00 pm, Taylor Singletary <[email protected]> > wrote: > > > > > > > > > By running on Google App Engine, or any host where you share IP addresses > > with another service, you're going to be at a disadvantage when it comes to > > abuse detection -- my advice would be to ensure you have a queue system in > > place for API actions you take (really any application servicing anywhere > > near as many users as you do should have this in place), especially actions > > applied in bulk -- you will have times that you need to queue up your > > actions until you can resume making requests -- the best way to detect if > > you can resume making requests is by intermittently trying a single item at > > the top of the queue once every few seconds, increasing the duration you > > wait with every failed request. > > > You never want to continue bursting when faced with an error like this, it > > would only make your application appear more abusive to the metrics-oriented > > unfeeling eye of an abuse detection algorithm. > > > @episod <http://twitter.com/episod> - Taylor Singletary > > > On Wed, Apr 6, 2011 at 8:47 AM, nischalshetty > > <[email protected]>wrote: > > > > Hi, > > > > It's my apphttp://justunfollow.comIt'sbeen running from more than a > > > year now. I did not see any sudden increase in traffic or any of that > > > sort. It's hosted on the Google Appengine and there were 2 cases in > > > the entire year when appengine ips were blocked by twitter. > > > > I have more than 200,000 users. Your advice would be greatly > > > appreciated. I do not make use of any search or trends api. > > > > -N > > > > On Apr 6, 8:41 pm, Taylor Singletary <[email protected]> > > > wrote: > > > > Unfollowing is not "rate limited" by the API, but we have organic limits > > > on > > > > most write actions service-wide to prevent certain kinds of bursty > > > behavior. > > > > Best to back off from retrying requests when you get an error like this > > > for > > > > an exponentially increasing amount of time -- first 30 seconds, then a > > > > minute, then a few minutes, then 10 minutes, etc. > > > > > @episod <http://twitter.com/episod> - Taylor Singletary > > > > > On Wed, Apr 6, 2011 at 8:31 AM, nischalshetty <[email protected] > > > >wrote: > > > > > > I am getting this for the Unfollow method. This shouldn't happen for > > > > > the unfollow API. Can someone at twitter look into it? > > > > > > -N > > > > > > On Apr 6, 8:24 pm, nischalshetty <[email protected]> wrote: > > > > > > 420:Returned by the Search and Trends API when you are being rate > > > > > > limited (http://dev.twitter.com/pages/rate-limiting). > > > > > > Returned by the Streaming API: > > > > > > Too many login attempts in a short period of time. > > > > > > Running too many copies of the same application authenticating with > > > > > > the same account name. > > > > > > > I'm getting the above error. It's in large numbers. Can someone > > > > > > help? > > > > > > -- > > > > > 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 > > > > -- > > > 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 -- 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
