Re: [twitter-dev] Re: Rate limits should be resetting now
Great news. I'm crossing my fingers too. isaiah http://twitter.com/isaiah On Jul 7, 2010, at 8:32 PM, Raffi Krikorian wrote: > we are currently sitting at 100% - so 350 calls/hour on oauth, and 150 > calls/hour on basic auth. fingers crossed! > > On Wed, Jul 7, 2010 at 6:42 PM, isaiah wrote: > Does this mean a return to previous rate limits as well? Or are we > still getting the squeeze? > > Isaiah > > On Jul 7, 5:54 pm, themattharris wrote: > > Hey everyone, > > > > We've been working on the rate limit issue which has been affecting > > many of you and believe we now have it fixed. As the issue affected > > people in different ways we want to be check your applications are > > working again. > > > > If your rate limit is still not resetting please email a...@twitter.com > > the following information: > > > > * The IP of the computer which is making the requests > > * A username you are making requests for > > * The time you tried to make the request > > * The request you were trying to make > > * Any response headers you received > > > > Thanks, > > Matt > > > > -- > Raffi Krikorian > Twitter Platform Team > http://twitter.com/raffi
Re: [twitter-dev] Re: Rate limits should be resetting now
Quoting Raffi Krikorian : we are currently sitting at 100% - so 350 calls/hour on oauth, and 150 calls/hour on basic auth. fingers crossed! Seems to be working fine here at the Bar Nothing Ranch - I'm getting "Bad Gateway 502" errors but between instances of those, I'm getting 150 calls per hour unauthenticated. On Wed, Jul 7, 2010 at 6:42 PM, isaiah wrote: Does this mean a return to previous rate limits as well? Or are we still getting the squeeze? Isaiah On Jul 7, 5:54 pm, themattharris wrote: > Hey everyone, > > We've been working on the rate limit issue which has been affecting > many of you and believe we now have it fixed. As the issue affected > people in different ways we want to be check your applications are > working again. > > If your rate limit is still not resetting please email a...@twitter.com > the following information: > > * The IP of the computer which is making the requests > * A username you are making requests for > * The time you tried to make the request > * The request you were trying to make > * Any response headers you received > > Thanks, > Matt -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Rate limits should be resetting now
we are currently sitting at 100% - so 350 calls/hour on oauth, and 150 calls/hour on basic auth. fingers crossed! On Wed, Jul 7, 2010 at 6:42 PM, isaiah wrote: > Does this mean a return to previous rate limits as well? Or are we > still getting the squeeze? > > Isaiah > > On Jul 7, 5:54 pm, themattharris wrote: > > Hey everyone, > > > > We've been working on the rate limit issue which has been affecting > > many of you and believe we now have it fixed. As the issue affected > > people in different ways we want to be check your applications are > > working again. > > > > If your rate limit is still not resetting please email a...@twitter.com > > the following information: > > > > * The IP of the computer which is making the requests > > * A username you are making requests for > > * The time you tried to make the request > > * The request you were trying to make > > * Any response headers you received > > > > Thanks, > > Matt > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Rate limits should be resetting now
Does this mean a return to previous rate limits as well? Or are we still getting the squeeze? Isaiah On Jul 7, 5:54 pm, themattharris wrote: > Hey everyone, > > We've been working on the rate limit issue which has been affecting > many of you and believe we now have it fixed. As the issue affected > people in different ways we want to be check your applications are > working again. > > If your rate limit is still not resetting please email a...@twitter.com > the following information: > > * The IP of the computer which is making the requests > * A username you are making requests for > * The time you tried to make the request > * The request you were trying to make > * Any response headers you received > > Thanks, > Matt
