Re:I think Twitter’s OAuth-only Access is a Waste of Time
by bonzoesc on Friday September 03, 2010 @10:45PM
(#1661856)
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
by decklin on Friday September 03, 2010 @10:35PM
(#1661838)
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.
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/blog/archives/2009/03/29/oauth-explaine... .
I'll admit getting started with OAuth takes some time to ramp up at first, but that ramp up time gets smaller each subsequent app.