3 ms·
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 do
by ck2 16y ago
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)
- zmoazeni 16y agoI 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/ http://twitter.rubyforge.org/ . And aside from a couple hiccups, I haven't had any problems with http://code.google.com/p/oauthconsumer/wiki/UsingOAuthConsumer 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).
- patrickaljord 16y agoYes, 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.
- megafotze 16y agothat PIN is just wrong. in my app I am opening the auth page in a web view and then parse the html of that web view to get the pin. an alternative is to register a custom url scheme like myapp:// but for that you have to email twitter's api team