Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I think Twitter’s OAuth-only Access is a Waste of Time

simplechatter.com

Post reply on HN
Print view View original

31–33 of 33 posts

Re: I think Twitter’s OAuth-only Access is a Waste of Time

#31

Post by dho »

jackowayed wrote: post #7

OAuth is also a huge pain for those "I just want to write a little Twitter API script in 5 minutes" things. To the extent that I've thought about writing a couple lately, but chose not to because I didn't want to deal with OAuth (and they were scripts I'd want to work in the future). It seems like there should be some solution that lets me use basic auth for those little scripts. Maybe tell Twitter IP's from which I…

For a single-user use case you could use http://dev.twitter.com/pages/oauth_single_token which doesn't require you to go through the OAuth token acquisition dance.

Re: I think Twitter’s OAuth-only Access is a Waste of Time

#32

Post by megafotze »

patrickaljord wrote: post #6
ck2 wrote: post #3

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)

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.

that 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

Post reply on HN