Thanks for clarifying ^^
Arthur.
2010/6/2 Taylor Singletary
> Hi Arthur,
>
> Indeed it is a Quest.
>
> You don't need to do this entire round trip every single time. In Twitter's
> OAuth implementation, when we respond with the access token to you in the
> access token step, we also include the
Hi Arthur,
Indeed it is a Quest.
You don't need to do this entire round trip every single time. In Twitter's
OAuth implementation, when we respond with the access token to you in the
access token step, we also include the screen_name and id of the user. You
in turn should store the id, screen_nam
After some work (and some help from the group) my implementation works,
but...
The QUEST to get an access token
1. app gets a request token from twitter
2. user clicks a button on the ap
3. app opens a twitter page, user types username/password
4. twitter gives user a PIN
5. user u
