Closed GoogleCodeExporter closed 9 years ago
Hi,
Please open pidgin, go to Accounts, edit twitter account.
which authentication method is in use?
If it is not OAuth, try using OAuth, see if that works.
Original comment by andresen.nils@gmail.com
on 22 Apr 2011 at 1:07
[deleted comment]
[deleted comment]
[deleted comment]
Hi,
I managed to let it work. So solved for me, but pidgin still crash if some
other users are doing same mistake.
I used my e-mail instead of my username twitter. Pidgin was trying to connect
to my mail server, instead of twitter.
Thank.
Original comment by Claude.C...@gmail.com
on 22 Apr 2011 at 1:43
Hm.
Just to be sure: Was this using the OAuth authentication or HTTP ?
Original comment by andresen.nils@gmail.com
on 22 Apr 2011 at 4:12
I have tested with the 3 methods when using my e-mail instead of my twitter
username.
OAuth: Crash
XAuth: Did not crash, but no message that username is wrong, or any alert to
say that can not connect.
HTTP basic auth: Crash
How to reproduce the problem?
0. Start pidgin
1. Configure account with protocol "Twitter IM"
2. User name: test@test.com
3: password: whatever
4: Select login method (I have tested all)
5: Use other defaults value.
6: Stop pidgin.
7: Start pidgin
8: Activate account
9: Wait a while...
My account.xml file
<account>
<protocol>prpl-mbpurple-twitter</protocol>
<name>test@test.com</name>
<password>whatever</password>
<statuses>
<status type='available' name='En ligne' active='true'>
<attributes/>
</status>
<status type='unavailable' name='Unavailable' active='false'>
<attributes/>
</status>
<status type='offline' name='Déconnecté' active='false'>
<attributes/>
</status>
</statuses>
<settings>
<setting name='twitter_auth_type' type='string'>mb_oauth</setting>
<setting name='twitter_hide_myself' type='bool'>1</setting>
<setting name='twitter_oauth_access_token_url' type='string'>/oauth/access_token</setting>
<setting name='twitter_use_https' type='bool'>1</setting>
<setting name='twitter_status_update' type='string'>/1/statuses/update.xml</setting>
<setting name='twitter_privacy' type='bool'>0</setting>
<setting name='buddy_icon' type='string'>d23eb7ec5ad1a9c050a851840d276ceed8a3f7bc.gif</setting>
<setting name='twitter_init_tweet' type='int'>15</setting>
<setting name='buddy_icon_timestamp' type='int'>1303492309</setting>
<setting name='twitter_user_timeline' type='string'>/1/statuses/user_timeline.xml</setting>
<setting name='twitter_public_timeline' type='string'>/1/statuses/public_timeline.xml</setting>
<setting name='twitter_hostname' type='string'>api.twitter.com</setting>
<setting name='use-global-buddyicon' type='bool'>1</setting>
<setting name='twitter_oauth_authorize_token_url' type='string'>/oauth/authorize</setting>
<setting name='twitter_replies_timeline' type='string'>/1/statuses/mentions.xml</setting>
<setting name='twitter_global_retry' type='int'>3</setting>
<setting name='twitter_friends_timeline' type='string'>/1/statuses/home_timeline.xml</setting>
<setting name='twitter_verify' type='string'>/1/account/verify_credentials.xml</setting>
<setting name='twitter_oauth_request_token_url' type='string'>/oauth/request_token</setting>
<setting name='twitter_msg_refresh_rate' type='int'>60</setting>
</settings>
<settings ui='gtk-gaim'>
<setting name='auto-login' type='bool'>0</setting>
</settings>
<current_error/>
</account>
Original comment by Claude.C...@gmail.com
on 22 Apr 2011 at 5:17
Ok, I finally managed to reproduce this problem.
The HTTP basic auth crash is due to Issue#230,
The „XAuth-nothing-happens” I can confirm - not sure why, though.
This is material for another issue, I think.
The OAuth crash has been fixed in r383
Original comment by andresen.nils@gmail.com
on 30 Apr 2011 at 9:49
XAuth has been removed as a selection in r298 - so this is no longer an Issue,
either
Original comment by andresen.nils@gmail.com
on 30 Apr 2011 at 10:08
Original issue reported on code.google.com by
Claude.C...@gmail.com
on 22 Apr 2011 at 10:10Attachments: