Live data from Hacker News

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

simplechatter.com

21–30 of 33 posts

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

#21
post #17

I wrote a simple script to post an RSS feed that my university uses to twitter. (Actually, I hacked up Stammy's It currently has about 190 followers, but it used Basic Auth so it stopped working on Thursday. Rather than switching to OAuth, I'm tempted to just write a mechanize script to make posts using the web interface. Has anybody tried this approach?

I've written such a script to hit the website directly. That "API" is far flakier than the basic auth version.

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

#22

Seems like this author just doesn't realize how painful migrating to OAuth is for a service provider. Of course xAuth isn't a real security improvement to HTTP Basic. But it forces everyone to support auth that isn't inherently broken. So once Twitter stops receiving many xAuth requests, they can just turn it off. The migration to OAuth 2 will be interesting though. All the existing clients will have the right kind o…

joseph, you have a good point about how large of a task migrating all service providers from Basic to OAuth is. And I have to give Twitter Support credit for their work helping developers along the migration.

But your argument still doesn't explain why Twitter's supported service still uses xAuth. Or Twitterrific (and they have a significant market share). What is blocking them from migrating from Basic to non-xAuth OAuth?

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

#23
post #14

I'll grant you that xAuth is a little convoluted. With that said, Twitter deserves credit for being unprecedentedly accommodating and transparent during the transition away from basic auth. It is obviously in their best interest not to break applications, but this hasn't stopped other social networks cough from yanking the rug from underneath scores of apps with little to no warning.

danhak, you make a good point. And I should have probably specifically mentioned that. Twitter Support has really been going the extra mile to help developers make the migration.

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

#24
>"I just want to write a little Twitter API script in 5 minutes"

In that case you would use Out-of-band/PIN Code Authentication. See http://dev.twitter.com/pages/auth_overview.

For Pythonistas, my little Twitter API script uses tweepy.py. Thanks to http://jmillerinc.com/2010/05/31/twitter-from-the-command-li... for the steps involved. As an exercise, you could scrape the required PIN with beautifulSoup or similar code to eliminate one step.

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

#25
I have a non-web, non-desktop based twitter app with a couple thousand users and just haven't had the time available to figure out how to get it doing newAuth.

xAuth seems like it'd work, but, as stated in the article, that involves me going through some hoops to get back to this level of security. woo.

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

#26
post #8

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…

One pain point I've had since switching from Basic Auth has the lack of debugging via a terminal and curl. That was pretty useful. For Ruby-minded folks there's http://github.com/marcel/twurl which is effectively curl that uses OAuth - though it isn't the same. John Nunemaker wrote a tutorial on how to get get up and running with OAuth pretty quickly (though it is for the Ruby/Rails audience) http://railstips.org/blo…

I wrote http://github.com/decklin/curlicue for precisely this reason. It's kind of a hack (shell script!), but I've gotten some mileage out of it.

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

#27
post #8

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…

One pain point I've had since switching from Basic Auth has the lack of debugging via a terminal and curl. That was pretty useful. For Ruby-minded folks there's http://github.com/marcel/twurl which is effectively curl that uses OAuth - though it isn't the same. John Nunemaker wrote a tutorial on how to get get up and running with OAuth pretty quickly (though it is for the Ruby/Rails audience) http://railstips.org/blo…

It really couldn't be much easier with the twitter gem, and it's way easier to clean up after an "oh shit I left credentials in that public script" moment; just re-generate the secrets on the twitter site.

https://gist.github.com/cfc477a0c5895e8bd1bd

Wrote this when I was drunk to prove a point.

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

#28
post #17

I wrote a simple script to post an RSS feed that my university uses to twitter. (Actually, I hacked up Stammy's It currently has about 190 followers, but it used Basic Auth so it stopped working on Thursday. Rather than switching to OAuth, I'm tempted to just write a mechanize script to make posts using the web interface. Has anybody tried this approach?

You could just use http://twitterfeed.com. Unless of course your script modifies the RSS data significantly before posting it.

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

#30
Could it be that Twitter is going the route of Apple? This raises the barrier to entry just enough to keep out developers who are just goofing around.

Otherwise, no, I don't see it. I know that I'm less inclined to write a little hack to work with Twitter without basic auth.

Post reply on HN