Twitter's new oauth feature has killed Pino 0.2 (AND Gwibber, too) ... but oauth support is coming to 0.3 ... and on a related note, is oauth trying to KILL ME?
Is Twitter's new oauth feature responsible for this annoying login box when I go to Twitter.com?
I ignore Twitter and Identi.ca for weeks at a time. Sure I have feeds from my blog going from one to the other, but I pretty much stay away from Twitter, Identi.ca and Facebook (the latter of which I also feed automatically).
So today I figure I'll look in on Twitter and Identi.ca via the Pino microblogging client that I installed in my Fedora 13 Xfce system. Pino is in the default GNOME desktop but not in the Xfce spin.
Anyway, Pino just hangs there when I start it. So I go to Twitter and do a search, eventually learning that it's something called "oauth" that is breaking Pino.
On the Pino site, a message says the app will have oauth support in 0.3, so I'm not terribly worried. I can live without a microblogging client until then. (We still have HootSuite, which is about to start charging all but the most casual user, and which due to its extreme usefulness we might just pay for at the shop here.)
Also ... I've heard Gwibber is affected as well.
Here's the important part of this entry, which I've wisely saved for the bottom: Is this oauth thing responsible for the annoying password box that keeps popping up at http://twitter.com? (see picture above)
2 Comments
Leave a comment
About this blog
That box appears because twitter is requesting a Basic HTTP Authentication from the browser. That should just be a misconfigurtion.
Summing up, no OAuth is not responsible for that box and no OAuth will not kill you :)
Thanks for the info on the Twitter login box. All I know is I don't like it.