Closed GoogleCodeExporter closed 9 years ago
Hi,
thanks for the report.
You describe the case: "Home" works, the next day "Work" does not. (Until a
reinstall)
Does this also happen "the other way around" ?
i.e. "Work" works, newt day "Home" does not ??
Could you please - on the machine that does not work - start pidgin in debug
mode, reproduce the problem and attach the log (i.e. on the ubuntu machine
start "pidgin -d > pidgin.log") ?
Thanks.
Original comment by andresen.nils@gmail.com
on 7 Feb 2011 at 12:04
>Does this also happen "the other way around"?
Yes, it happend
Here is a debug logs from Windows and Ubuntu machine
Original comment by ceeka...@gmail.com
on 8 Feb 2011 at 5:16
Attachments:
Ok, thanks. I'll look into that.
In the meantime, you do not need to reinstall, to get a new OAuth request.
Simply open pidgin, accounts-menu, select the TwitterIM account. The submenu
shows "Remove access credential". That should do the trick. (Maybe a bit
simpler than the reinstall...)
Original comment by andresen.nils@gmail.com
on 8 Feb 2011 at 6:41
Thanks, don`t know about that.
For now it works on "Work" and i`ll try at "Home" in evening.
Original comment by ceeka...@gmail.com
on 8 Feb 2011 at 8:15
What distubs me in those logs are all those http 404 errors...
Could you please check the TwitterIM account settings?
The "Account verification path" should point to
"/account/verify_credentials.xml" please check if yours is different.
Original comment by andresen.nils@gmail.com
on 8 Feb 2011 at 7:52
UPD: At "Home" after few reconnects appear new oAuth request. I put new code
and it successful connect to twitter. With options like at screenshoot 2.
I`ll try it at "Work" later.
Original comment by ceeka...@gmail.com
on 9 Feb 2011 at 2:09
UPD: At "WORK" its connected successful too. With options like at screenshoot 2.
Why by default uses options with "/1/" ? I think there is a trouble.
Original comment by ceeka...@gmail.com
on 9 Feb 2011 at 3:49
/1 is the new official API URL for Twitter.
Hmm... This reminds me. I think, with OAuth, it shouldn't allow user to have
multiple computer running the same app using different authentication key.
Twitter should see both your Home and Work as mbpurple and it should reject
another, duplicate OAuth access.
I'm curious why it worked by using different URL.
Original comment by somsaks
on 9 Feb 2011 at 4:00
somsaks, I did not know that - I am reading
http://dev.twitter.com/doc/get/account/verify_credentials now... btw: my
linux-installation does not use the "/1" whereas my windows installation does.
I am currently using bot at the same time (Home/Work) no problems..
the thing with "multiple computer running the same app using different
authentication keys" came to mind, yes. But I fount a twitter issue report
(currently unable to find it again) stating that twitter will re-send the
oauth-token if the "same" app requests another token. So given that both
installs "Home" and "Work" should use the same token...
Original comment by andresen.nils@gmail.com
on 9 Feb 2011 at 6:48
I am unable to reproduce this phenomenon.
I use three machines win, gentoo, ubuntu - everything is fine.
Are you still having problems ceeka?
Original comment by andresen.nils@gmail.com
on 15 Feb 2011 at 7:33
Original comment by andresen.nils@gmail.com
on 22 Apr 2011 at 4:37
Original issue reported on code.google.com by
ceeka...@gmail.com
on 4 Feb 2011 at 12:10