Well I've seen my rate limit has dropped to 175 calls per hour now
On Jun 24, 4:16 am, think0rdie mxe02...@gmail.com wrote:
if it means you won't expand Twitter's capacity itself,
movingratelimits for all clients is simply a bad news for us, end
users.
in effect, today I've got more API
Could you give more information on how you would lower a specific
user's limits?
For example my client does the following, this is of course simplified
api_requests_left = 0;
loop {
if(api_requests_left == 0) { update_request_limits(); } // hit your
server and ask my remaining limit, sleep
So what is going to be the time periods between changes. Is going to
be changed by the day,hour, minute? cause it can change like every 2
minutes it would be hard to tell a client that they had 50 more calls
one minute and 0 the next. And what is going to be our interval of
change at minimum
if it means you won't expand Twitter's capacity itself,
moving rate limits for all clients is simply a bad news for us, end
users.
in effect, today I've got more API errors on HootSuite than ever.
in other words, Twitter experience simply has become worse.
