twidge 0.99.4 does not work with the updated twitter API

Bug #628725 reported by Tom Henderson
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
twidge (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: twidge

All attempts to use twidge with twittter are failing with a code 401. This began sometime in the last 8 hours. From what I have been able to figure out, the twitter API has changed. Newer versions of twidge have apparently fixed this problem. it appears the current twidge release is 1.0.5

I am running 9.10 with twidge 0.99.4. Package manager does not indicate an update is available for twidge.

Revision history for this message
sldev slnull (slashdevslashnull9) wrote :

I have the same issue

curl: (22) The requested URL returned error: 401
twidge: user error (("curl",["-A","twidge v1.0.0; Haskell; GHC","-s","-S","-L","-y","60","-Y","1","--retry","2","-f","--user","xxxx:yyyy","https://twitter.com/statuses/friends_timeline.xml?page=1"]): exited with code 22)

Revision history for this message
Kai Jauch (kaijauch) wrote :

From https://github.com/jgoerzen/twidge/wiki/FrequentlyAskedQuestions

"Fixing 401 Errors starting October 25, 2010 – twidge 1.0.5 and earlier

Twitter pulled a fast one on us: they revoked Twidge’s API key for some fake security reason. See http://blog.nelhage.com/2010/09/dear-twitter/ for why this is wrong-headed.

You have three options:

   1. Upgrade to twidge 1.0.6
   2. You can obtain the OAuth.hs file from http://github.com/jgoerzen/twidge/raw/9421da8999efb3322e86c30f8f026af3529576e3/OAuth.hs, put it in place of your existing OAuth.hs in the top level of the twidge distribution, and recompile.
   3. You can go to http://dev.twitter.com, register your own app, and set oauthconsumerkey and oauthconsumersecret in your config file to the values given to you by Twitter."

Maverick contains version 1.0.2 (which doesn't work), Natty 1.0.6, so it should work in Natty.

Changed in twidge (Ubuntu):
status: New → Confirmed
Revision history for this message
Mark Hobley (markhobley) wrote :

This has started happening again since 13th October 2012 with version 1.0.8. Has twitter updated something and broken the client again?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.