400 Rate limiting: you have reached the limit requests

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run pino.
2. Leave it alone for some time (a few hours to a day), until you see a warning 
sign on the bottom bar.
3. Try to do anything on pino, such as seeing previous tweets, refreshing your 
timeline, or clicking on a username to see their timeline.

What is the expected output? What do you see instead?
I expect the action to be completed withouth a problem. Instead I see the 
following error message on the bottom bar of the window:
"400 Rate limiting: you have reached the limit requests"
I haven't found this very annoying problem on any other Twitter client running 
on the same hardware.

What version of the product are you using? On what operating system?
pino 0.2.11 on Ubuntu 10.04.

Please provide any additional information below.

Original issue reported on code.google.com by fibonacc...@gmail.com on 23 Aug 2010 at 6:40

[GoogleCodeExporter]

I can confirm this bug for pino 0.2.11 on debian. According to 
http://dev.twitter.com/pages/rate-limiting the rate limit for Basic Auth is 150 
requests per hour. My update interval is set to 5 minutes, so pino would have 
to make at least 13 requests per update to exceed the rate limit. I'll set the 
update interval to 10 minutes, see if that's better.

Original comment by n...@uschok.de on 24 Aug 2010 at 1:45

[GoogleCodeExporter]

The 10 minute update interval doesn't seem to trigger the rate limit.

Original comment by n...@uschok.de on 24 Aug 2010 at 2:52

[GoogleCodeExporter]

Six minutes does still trigger it, though.

Original comment by fibonacc...@gmail.com on 26 Aug 2010 at 3:27

[GoogleCodeExporter]

Same thing for seven minutes. It means pino is making more than 17 requests per 
update.
Also, at this point with rate limiting pino has become unusable, since when the 
limiting wears off I've got more incoming tweets at the same time than I can 
read before the next update.

Original comment by fibonacc...@gmail.com on 30 Aug 2010 at 11:37

[GoogleCodeExporter]

#313 is related to this.  The switch to OAuth needs to happen. Since according 
to Twitter, today is the last day basic auth works.

Original comment by matthew....@gmail.com on 31 Aug 2010 at 12:20