gwibber-bugs team mailing list archive

[Khurshid Alam <sunnysigara+launchpad@xxxxxxxxx>]

Public bug reported:

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.

** Affects: gwibber
     Importance: Undecided
         Status: New

** Summary changed:

- Twitter doesn't work anymore after retirement of v1 api
+ Twitter doesn't work anymore after retirement of v1 api on 12.04

** Description changed:

  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 twitter feed.
+ Hence it is unable to receive any tweets.

-- 
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

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