News for hackers. Stuff that matters.
Re:I think Twitter’s OAuth-only Access is a Waste of Time by ck2 on Friday September 03, 2010 @04:35PM (#1661052)
Twitter's OAuth is a total pain to implement.

If they had just upgraded to OAuth 2.0 like Facebook recently launched, I'd be happy.

Facebook's OAuth can be done in like 10-20 lines of code. Twitter's takes like 100 (in PHP+Curl).

(essentially OAuth 2.0 just relies on https SSL instead of directly encrypting tokens via code before they are sent)

Re:I think Twitter’s OAuth-only Access is a Waste of Time by zmoazeni on Friday September 03, 2010 @04:41PM (#1661081)
I haven't worked with OAuth 2.0 yet, but I've been meaning to take a look at it with Facebook's update.

However in Ruby/Rails OAuth isn't that bad using http://twitter.rubyforge.org/ . And aside from a couple hiccups, I haven't had any problems with http://code.google.com/p/oauthconsumer/wiki/UsingOAuthConsum... on iPhone/iPad (I'm using the Browser redirect and re-launching the application from a custom application protocol).

Re:I think Twitter’s OAuth-only Access is a Waste of Time by patrickaljord on Friday September 03, 2010 @04:47PM (#1661103)
Yes, the most painful part is having to copy the pin number manually for non web apps, a real pain. I read twitter is working on the oauth 2.0 spec themselves with facebook and google, so we may get some relief soon.