Rate limit exceeded. Cannot log in.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Starting the app
2.
3.

What is the expected output? What do you see instead?
I expect the application to let me log in using my twitter credentials, 
however I receive the error:  Rate limit exceeded.  Clients may not make 
more than 70 requests per hour.  Please try again in a few minutes.

What version of the product are you using? On what operating system?
Witty 0.1.7 Beta 1 on Windows Vista SP1

Please provide any additional information below.

Original issue reported on code.google.com by tlope...@gmail.com on 28 Mar 2008 at 6:53

[GoogleCodeExporter]

right now login() is using the Twitter API Show method which costs 1 rate limit 
hit.
When the user has reached the rate limit, they can't login.

Need to make a non Twitter api call that does not count toward rate limit to at 
least
let the user login.

Once login, they wont be able to get new tweets until the rate limit has 
subsided.
Because of this, I'm marking this issue as low.

Thoughts?

Original comment by alan...@gmail.com on 28 Mar 2008 at 9:49

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Issue 135 has been merged into this issue.

Original comment by jongallo...@gmail.com on 10 Jan 2009 at 6:50

[GoogleCodeExporter]

This is the first attempt at solving this. I've made login use 
verify_credentials
which (from my tests with cURL) doesn't use an API hit. If that changes,
rate_limit_status is documented not to use an API hit. 

I've also refactored the pattern of creating a HttpWebRequest.

Finally, when a 400 status code is hit, the error message should now include a 
x/100
message about the rate limit. It would be nice to refactor the entire catch 
block
into a method, but I didn't want to make that big of a change yet. 

I still need to get testing on this. It works for regular usage, but I don't 
know if
it actually stops the real problem.

TODO:
* Include time of rate limit reset in the error message
* Tooltip with rate limit on the refresh button
* Cache this request for speed (extra requests don't matter for the API request)

I'll follow up with Twitter to see if verify_credentials is meant to use a API 
hit or
not.

Original comment by james.deville on 12 Jan 2009 at 8:34

Attachments:

• login.patch

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This fixes the messaging of the rate limit error, and it uses a different 
method to
manually add the basic auth header to the request. It now works behind a 
proxy!!!!!

Original comment by james.deville on 17 Jan 2009 at 3:28

Attachments:

• networkrefactor.patch

[GoogleCodeExporter]

Original comment by james.deville on 8 Feb 2009 at 4:53

• Changed state: Fixed

[GoogleCodeExporter]

Not fixed. I have this issue in version 2.1.2.0 and the rate limit is 100. What 
is a 
rate limit anyway?

Original comment by a...@harborcomputerservices.net on 13 Mar 2009 at 5:54

[GoogleCodeExporter]

The rate limit is how many times we can contact Twitter. Are you getting this 
problem 
after using Witty for a while? Or right when you open it. Do you have any other 
twitter 
clients running at the same time?

Original comment by james.deville on 14 Mar 2009 at 6:17

[GoogleCodeExporter]

I have version 2.0.4.18444 and started seeing this error just today.  My limit 
is 75, apparently, which seems quite low even if it did have to be there.  
Can't log in, obviously can't post, etc.; not running any other Twitter 
clients.  It appeared after restarting the computer when I updated Adobe 
Acrobat just now, but I hadn't changed anything else.

Original comment by poet.isc...@gmail.com on 6 Jul 2010 at 5:48

[GoogleCodeExporter]

If anyone else runs into this, try reinstalling.  Appears to have fixed it for 
me.

Original comment by poet.isc...@gmail.com on 7 Jul 2010 at 3:00

[GoogleCodeExporter]

Twitter has been raising and lowering their API limits as early as last week to 
counter their latest round of increased traffic.  The API limit was indeed 75 
requests per hour until some point late yesterday (CDT); after that it was 
raised to 150 and as of this post appears to be hovering at that level.  In 
poet's case, the likely scenario (especially judging by the timestamps) isn't 
that the reinstall helped but that he left the account alone long enough for 
the hour to recycle.

You can check the limit with this URL (I recommend looking at the source): 
http://api.twitter.com/1/account/rate_limit_status.xml

Original comment by NickTabick on 7 Jul 2010 at 3:22