70 API calls per hour limit exceeded

I think twitter messed with settings to try and keep from being flooded. And they set limits TOO LOW!!! Hello twitter..fix this PLEASE...

PS: the rate limit is now 30 according to the xml file. So that means that I can only get 30 tweets per hour? come on twitter that is retarded. this is no way to treat a new customer.

I'm having the problem with sending 0 tweets and making 1 request after 12 hours of idle time.

It does not seem to be related to the rate limit. My account just seems to be constantly "over" the limit without making a request.

Just a quick note to say that sending tweets does not eat into your limit. Neither does sending a direct message.

From the API documentation on Rate Limits:

POST requests (ex: updating status, sending a direct message) also do not count against the rate limit.

One last call for assistance. Twitter...change this limit of 30 or I am taking all my contacts to Jaiku! You do not answer support emails for days. Very bad service!!

It seems that Twitter has reduced the number of requests to 30, as photolarry noted. That doesn't mean you only get 30 tweets an hour, it means anything requests data via the API can only make 30 requests an hour. Sure, that means you will miss stuff, but that's not uncommon anyway.

I'm sure this is just part of the scaling back that twitter is currently doing to help recover. Hopefully they'll fix it soon.

ok I got a reply from Evan, finally. I have changed my client to only check for updates every 15 minutes instead of every 5 to bandaid this for now. But I made it clear they really should up this limit unless someone has offended with flooding. They claim their servers are lacking and cannot handle the demand. I suggested placing ads on their site.

Setting Twitterrific to 15 minute refresh makes it nearly pointless. I always though 70 an hour was too few considering you like to refresh after posting. Please bring it back up to 70 or higher.