Open GoogleCodeExporter opened 8 years ago
I have same problem, I can't view my timeline, mentions, directo messages. Only
works new tweets and see user profiles. I'm using Pino 0.2.10 on Fedora 13 x64.
This problem begin 5 or 7 hours ago.
Original comment by gotenc...@gmail.com
on 1 Sep 2010 at 12:40
It's due to twitter turning off basic auth. Pino needs to switch to oauth, or
xauth (I hear the latter is better?)
Original comment by nosr...@gmail.com
on 1 Sep 2010 at 12:43
This is because Twitter has revoked the default auth method, and only allows
OAuth, that Pino doesn't implements yet on version 0.2.X
Original comment by JoseL.Segura
on 1 Sep 2010 at 8:39
Well, that was kinda redundant.
Original comment by nosr...@gmail.com
on 1 Sep 2010 at 12:56
Does anybody know when version 0.3 is out?
Original comment by relga...@gmail.com
on 1 Sep 2010 at 12:57
I'm kinda disappointed that the devs didn't bring out an OAuth-ready version of
Pino in time. Now I look like an ass to all the people I recommended to switch
from Gwibber to Pino. >:-O
Original comment by igi...@gmail.com
on 2 Sep 2010 at 8:03
Gwibber has stopped working too. However, it seems there is a working (although
unstable) version which does support OAuth.
Original comment by fibonacc...@gmail.com
on 2 Sep 2010 at 8:30
Pino was almost the perfect twitter client, it's a shame it didn´t survived
the OAuthpocalypsis :(
Original comment by josernes...@gmail.com
on 2 Sep 2010 at 2:46
Will you fix this, my dear devs?
Original comment by dottorbl...@gmail.com
on 4 Sep 2010 at 9:50
@dottorblaster
It's already fixed in 0.3, it's just there's nothing more than screenshots of
it to be had.
Original comment by nosr...@gmail.com
on 4 Sep 2010 at 10:04
Thank you for the very quick response nosrepa.
So, I feel relaxed now but... when will be release this 0.3?
Original comment by dottorbl...@gmail.com
on 4 Sep 2010 at 11:00
i will release my twitter-only build (im not original developer) in next days
(say, monday)
Original comment by lost.chi...@gmail.com
on 4 Sep 2010 at 3:00
Original issue reported on code.google.com by
nosr...@gmail.com
on 31 Aug 2010 at 10:10