Quick and Dirty Twitter oAuth Manual

For those developers who are new to oAuth but too A.D.D. to read the ridiculously long "Beginner's Guide to oAuth," I present to you this handy guide.  This was authored by @pud with help from from @harper.

What's oAuth?
oAuth enables Twitter apps to use Twitter's API without knowing user passwords -- because nobody likes giving out their password.  If you haven't already, go here to register your application with Twitter (that's where you'll find your "consumer keys").  You'll also want to find some oAuth libraries to make things easier -- all this stuff needs to be encrypted and whatnot.


STEP 1
Send your CONSUMER_KEY and CONSUMER_SECRET_KEY to http://twitter.com/oauth/request_token
Twitter responds with OAUTH_TOKEN and OAUTH_TOKEN_SECRET

STEP 2
Send the user to http://twitter.com/oauth/authorize?oauth_token=OAUTH_TOKEN
User clicks "Allow" and is transported to the "callback URL" (your site) that you specified when registering your app.

STEP 3
Send CONSUMER _KEY, CONSUMER_SECRET_KEY, OAUTH_TOKEN, and OAUTH_TOKEN_SECRET to http://twitter.com/oauth/access_token
Twitter responds with a new OAUTH_TOKEN and OAUTH_TOKEN_SECRET.  Save these values in your database and send them with API calls.