Modify ↓
Opened at 2014-02-23T16:20:58Z
Closed at 2014-02-23T20:35:02Z
#1133 closed defect (alreadydoingthat)
Twitter fires up errors 426 and 429
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | BitlBee | Version: | 3.2.1 |
Keywords: | Cc: | ||
IRC client+version: | hexchat 2.9.6 | Operating System: | Linux |
OS version/distro: | xubuntu 13.10 saucy |
Description
Using bitlbee 3.2-1.1 on xubuntu saucy. At first twitter downloaded the old twits to me and the friends list, then logouted with error 426. Changed the api url to the https one and requested oauth on suggestion by bitlbee itself. Now does the same but dies with error 429 (Rate limit exceeded). How do I overcome this problem of having loadsa people following? Is there even a way?
Thanks
Attachments (0)
Change History (1)
comment:1 Changed at 2014-02-23T20:35:02Z by
Resolution: | → alreadydoingthat |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
The main page says bitlbee 3.2.1 fixes twitter issues. 3.2-1.1 is just unfortunate naming used by ubuntu, that looks similar to 3.2.1 but the part after the dash is the package revision. So that's 3.2, ubuntu package revision 1.1.
You can update to the latest version using the APT repo here: http://code.bitlbee.org/debian/ - There's no repo for saucy yet but the raring one works fine, I've heard.
Just for completeness: error 426 means "upgrade required" which means you need to use https for all requests, and this required changes in the code, there's no workaround like changing api url. Error 429 just means you're reconnecting too fast.