search

mikeage / prpltwtr

libpurple plugin to add support for the twitter / status.net protocol
GNU General Public License v2.0
32 stars 18 forks source link

rate exceeded error #17

Open heynnema opened 9 years ago

heynnema commented 9 years ago

After running for a while, it disconnects and throws a "rate exceeded" error. I've tried reducing the update frequency from 1 minute to 2 minutes, with no change.

Any ideas?

Cheers, Al

mikeage commented 9 years ago

It's hard to say without a log.

heynnema commented 9 years ago

Please tell me how to find, or how to create, such a log file and I'll be glad to try and get it to you.

Cheers, Al

mikeage commented 9 years ago

https://developer.pidgin.im/wiki/TipsForBugReports#ObtainingaDebugLog

heynnema commented 9 years ago

Got the log. Where shall I post/upload/email it?

Cheers, Al heynnema at gmail

mikeage commented 9 years ago

pastebin.com? Make sure there's no private info there; I don't think prpltwtr prints anything secret but I don't know about any other protocols. Alternatively, you can email me at mikeage at gmail.

heynnema commented 9 years ago

Sent via email. Thanks Mike!

Cheers, Al

mekkim commented 9 years ago

Just want to add my +1 that I'm also getting rate limited pretty frequently. I've drastically increased the number of minutes for updates and it still seems to hit the limit within about 10 minutes.

mekkim commented 9 years ago

UPDATE: I've figured out what's going on. The timeline update config setting is being ignored. It's updating the timeline every 60 seconds (1min) regardless of the setting. Here's a log where I have it set to 10 minutes: http://pastebin.com/rJRavUy7 - You can see that at each minute at 44 seconds on the time stamp it refreshes the timeline and eats up another rate-limit count.

Here's a second log where I have the timeline update configuration set to 20 minutes: http://pastebin.com/eB5GGzaE - Once again, at each timestamp ending in 46 seconds every minute, you can see that the timeline refresh is triggered, ignoring the setting of 20 minutes.

This is probably why rate-limits are getting eaten up so fast. It seems like the Twitter servers are allowing 15 queries every 15 minutes (average of 1 per 60 seconds). That gets eaten up within 7 or 8 minutes with the various updates given that the timeline is continuously updating regardless of the settings.

Please let me know if I can provide any more information to help debug.

tumpio commented 9 years ago

There seems to be another option to set the timeline update interval. Righ click the "Home Timeline" and select "Edit settings..". There is "Update Interval" setting which was at 1 min even though I had set the option in the account settings to 30 min. hmm?

Edit: I'm not getting the rate exceeded warning anymore, after changing the "hidden" option. I think these two options should be merged for the reason that the one in the options menu doesn't work (or the other one in the "Timeline" options overrides it) and the default 1 min interval should be increased to 5-10 min.