We only use documented versioned api calls and seeing rate limit
issues. I've not been aplenty to use my account for hours. Change ip
address and it's fine


On Jul 6, 10:45 pm, Bruno Renié <bubu...@gmail.com> wrote:
> On Jul 6, 6:47 pm, "M. Edward (Ed) Borasky" <zn...@borasky-
>
> research.net> wrote:
> > Quoting goodtest <goodtest...@gmail.com>:
>
> > > We make only about 20-25 requests per hour. We didnt have any problems
> > > until today morning. And all of a sudden I am seeing "Rate limit
> > > exceeded. Clients may not make more than 75 requests per hour."
>
> > > This is Zimbra Collaboration Suite's Social Zimlet.
>
> > I am also seeing tweets from friends that Tweetdeck is running into  
> > problems. I don't have Tweetdeck, so I can't confirm it. Perfect storm?
>
> I had that problem too. I was using OAuth with old-style URLs, such
> as:
>
> https://twitter.com/direct_messages.json
>
> instead of:
>
> https://api.twitter.com/1/direct_messages.json
>
> The former started to gave me "Rate limit exceeded, don't do more that
> 75 req/hour" all the time (even after waiting for the reset time) and
> switching to the latter works as expected: the rate limit is 175
> requests per hour and the countdown actually works.
>
> So, if you're getting rate limit errors and you're using OAuth, make
> sure you're using the URLs documented onhttp://dev.twitter.com/doc,
> especially if your app is a bit old.
>
> Hope that helps,
> Bruno

Reply via email to