StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I have no precise recipe for twitter (not having done exactly that until now), but given that OAuth has a specification describing the different possible flows, I'd try to enumerate each of them for the case at hand, and try to automate the interaction.</p> <p>To guide you, here are a few pointers to relevant information:</p> <ul> <li><a href="http://apiwiki.twitter.com/OAuth-FAQ" rel="nofollow noreferrer">OAuth/Twitter FAQ</a></li> <li><a href="http://www.hueniverse.com/hueniverse/2007/10/beginners-guide.html" rel="nofollow noreferrer">Beginner's Guide to OAuth</a></li> <li><a href="http://apiwiki.twitter.com/OAuth+Example+-+Ruby" rel="nofollow noreferrer">Twitter OAuth ruby example</a></li> <li><a href="http://stakeventures.com/articles/2008/02/23/developing-oauth-clients-in-ruby" rel="nofollow noreferrer">Developing OAuth clients in ruby</a></li> </ul> <p>Usually the flow for web based is different (as you have seen) whether the user has not given authorization to the client application: </p> <ul> <li>if the user has not yet given authorization to the client application then it is redirected to the service provider site <ul> <li>at the service provider is the user was not already logged in it is required to authenticate with his credentials</li> <li>once authenticated at the service provider it is required to authorize or deny authorization to the client application/service</li> <li>once he has given the authorize response it is sent back to the client site which can then get an access token </li> </ul></li> <li>if the user had already authorized the client application/service then it can use the access token to bypass those steps and access users' data/API at the service provider </li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload