search

jgoerzen / twidge

Command-line twitter/identica client [Haskell]
http://wiki.github.com/jgoerzen/twidge/
GNU General Public License v2.0
220 stars 29 forks source link

Parse error: unexpected EOF #8

Closed tinou closed 14 years ago

tinou commented 14 years ago

I just installed twidge from git (using rev edfa319045909a28d54777d719b2412a56483595). I ran cabal install, twidge setup, entered a pin number from the twitter website. I tested with twidge lsrecent and all I have is the following error "Parse error: unexpected EOF". With debug mode ($USER changed to XXX) :

$ twidge -d lsrecent
CP /home/XXX/.twidgerc exists? True
response: RspHttp {status = 401, statusLine = "", rspHeaders = , rspPayload = Empty}
Got doc: 
twidge: Parse error: unexpected EOF
jgoerzen commented 14 years ago

That 401 means "unauthorized." Try running "twidge setup" again; there's a chance something went wrong in the authorization phase. If that doesn't help, try running twidge -d setup to capture what's happening there.

tinou commented 14 years ago

Thanks for the quick reply. I tried again several times, and the same error keeps happening. Here is a trace of twidge -d setup. For "ttt....ttt" and "sss....sss", each instance refer to the same hex string.

Thanks

$ twidge -d setup
CP /home/XXX/.twidgerc exists? True

It looks like you have already authenticated twidge.
If we continue, I may remove your existing
authentication.  Would you like to proceed?

YES or NO: YES

Welcome to twidge.  We will now configure twidge for your
use with Twitter (or a similar service).  This will be quick and easy!

Please wait a moment while I query the server...

reqres params:
oauth_token=ttttttttt.....ttttttttt&oauth_token_secret=sssssss.......sssssss&oauth_callback_confirmed=true
OK, next I need you to authorize Twidge to access your account.
Please cut and paste this URL and open it in a web browser:

https://twitter.com/oauth/authorize?oauth_token=ttttttttt.....ttttttttt

Click Allow when prompted.  You will be given a numeric
key in your browser window.  Copy and paste it here.
(NOTE: some non-Twitter services supply no key; just leave this blank
if you don't get one.)

Authorization key: nnnnnnn
(False,True,oauth_token=ttttttttt.....ttttttttt&oauth_token_secret=sssssss.......sssssss&oauth_callback_confirmed=true)
Successfully authenticated!
Twidge has now been configured for you and is ready to use.
jgoerzen commented 14 years ago

Can you tell me if you have an oauth_data in your config file and what it looks like?

tinou commented 14 years ago

After twidge setup, my~/.twidgerc is like the following. The token and the token_secret fields (here anonymized) are the same as those that appeared during twidge setup.

[DEFAULT]
oauthaccesstoken: %(urlbase)s/oauth/access_token
oauthauthorize: %(urlbase)s/oauth/authorize
oauthdata: [("oauth_token","ttt...ttt"),("oauth_token_secret","sss...sss"),("oauth_callback_confirmed","true")]
oauthrequesttoken: %(urlbase)s/oauth/request_token
sendmail: /usr/sbin/sendmail
shortenurls: yes
urlbase: https://twitter.com
jgoerzen commented 14 years ago

Fix oAuth on twitter

identi.ca support in 8c4a9a0e8c5b24e52796d8b7efe010df6cc7565c broke it

Closed by e3d167234181a780cdd4adde1682cd6f8dadb94f