Red Hat Bugzilla – Bug 495159
Gwibber not displaying twitter timeline due to API change upstream requiring GET instead of POST
Last modified: 2009-04-21 20:51:47 EDT
Description of problem:
As of this morning, Twitter deprecated part of the API which Gwibber uses to query for timeline updates. This means that Twitter support is now broken in Gwibber.
While an official release hasn't been sent out yet, it is possible to patch Gwibber, based on the updates made upstream, and was wondering if it was possible to update Gwibber to temporarily fix this issue (until an official release is made).
The diff for the fix is available at:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Load Gwibber and add a Twitter account
2. Attempt to retrieve the timeline, which will fail with HTTP error 400
The timeline fails to load with HTTP error 400
The timeline and replies should load in the relevant tabs
Thanks for the reminder, was going to get to this later today but forgot ;)
gwibber-1.0.1-1.286bzr.fc10 has been submitted as an update for Fedora 10.
I've just installed the updated version and it works fine for me - thanks for fixing this Ian
For anyone else coming across this bug. You can tell if this affects you by going to the View menu -> Errors and looking for "Error 400" messages associated to the twitter account.
gwibber-1.0.1-1.286bzr.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-3556
I just installed gwibber.noarch 0:1.0.1-1.286bzr.fc10 and I can see my twitter feed again.
gwibber-1.0.1-1.286bzr.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.