4 ms·

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 coup

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 want to be able to use basic auth? It would be a bit of a pain since most people have dynamic IP's, but it would be better than nothing, and it would at least make it simple to run basic auth scripts on my VPS (which obviously has a static IP).

zmoazeni 16y ago
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 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-explained-and-what-it-is-good-for/ 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.
- decklin 16y ago
  I wrote http://github.com/decklin/curlicue 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.
- bonzoesc 16y ago
  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 https://gist.github.com/cfc477a0c5895e8bd1bd Wrote this when I was drunk to prove a point.
patrickaljord 16y ago
There's an oauth curl to write script quickly with oauth and curl http://code.google.com/p/oacurl/ http://code.google.com/p/oacurl/
mcantelon 16y ago
An opt-in, per user, enable of basic auth might be a nice thing, but probably a hassle for them to implement.
elliottkember 16y ago
I made a fun little app for this: http://simpleauthtwitter.heroku.com/ http://simpleauthtwitter.heroku.com/ it's not very complicated, but it might help.
dho 16y ago
For a single-user use case you could use http://dev.twitter.com/pages/oauth_single_token http://dev.twitter.com/pages/oauth_single_token which doesn't require you to go through the OAuth token acquisition dance.

zmoazeni 16y ago

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 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-explained-and-what-it-is-good-for/ 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.

decklin 16y ago
I wrote http://github.com/decklin/curlicue 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.
bonzoesc 16y ago
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 https://gist.github.com/cfc477a0c5895e8bd1bd Wrote this when I was drunk to prove a point.

patrickaljord 16y ago

There's an oauth curl to write script quickly with oauth and curl http://code.google.com/p/oacurl/ http://code.google.com/p/oacurl/

mcantelon 16y ago

An opt-in, per user, enable of basic auth might be a nice thing, but probably a hassle for them to implement.

elliottkember 16y ago

I made a fun little app for this: http://simpleauthtwitter.heroku.com/ http://simpleauthtwitter.heroku.com/ it's not very complicated, but it might help.

dho 16y ago

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