Yeah, this is not exactly my top priority right now. Ken, do you know offhand if 1.1 is implemented in later versions of gwibber? Can I just SRU a newer version or do I actually have to implement twitter 1.1 from scratch here?
-- You received this bug notification because you are a member of Gwibber Bug Heros, which is subscribed to Gwibber. https://bugs.launchpad.net/bugs/1190575 Title: Twitter doesn't work anymore after retirement of v1 api on 12.04 Status in Gwibber: New Status in “gwibber” package in Ubuntu: Confirmed Status in “gwibber” source package in Precise: Triaged Bug description: Gwibber does NOT work with twitter anymore as Twitter abandoned their v1 api. On Ubuntu 12.04 gwibber (3.4.2) still uses twitter api v1. This can be confirmed by running following commands: cat /usr/share/gwibber/plugins/twitter/__init__.py | grep 'API_PREFIX =' API_PREFIX = "https://api.twitter.com/1"; On twitter developer page it says: "Authenticated & unauthenticated requests to api.twitter.com/1/* will receive HTTP 410 Gone. Use API v1.1 instead." Hence it is unable to receive any tweets. To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/1190575/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~gwibber-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~gwibber-bugs More help : https://help.launchpad.net/ListHelp
