Open Stwissel opened 13 years ago
The message is self-explanatory , you exceeded the number of allowed API calls that twitter defines :) See http://dev.twitter.com/pages/rate-limiting#rest for more detailed information.
Sure running gwibber on the same machine is related , as "The REST API does user and IP-based rate limiting"
OK. Can I configure / read the limits somewhere, so I can give a "cowboy slow down" signal?
You cannot configure somehow the limits. But twitter API does provide some information about remaining allowed calls in response headers. I'll work on providing that feedback , back to the user so it is obvious how much more he can "Creepy" for that hour. Thanks for the suggestion ;)
Great. Nice little tool. Blogged about it here: http://www.wissel.net/blog/d6plinks/SHWL-8FHA6G
the "thesis" part is wrong but thanks anyway :)
Running it on Ubuntu 10.10 and get this error:
"Error while accessing twitter .The problem was : Rate limit exceeded. Clients may not make more than 150 requests per hour."
Could it be related to the fact that I run Gwibber too?