I actually miss read djMix and just saw "authorize" and not "authenticate". That being said when I was testing oauth/authenticate a few days ago I used the *exact* same code for both oauth/authorize and oauth/authenticate and both worked implying a return of a request token. It is possible that I was not paying attention and was using access tokens from an older session though. I'll double check later tonight.
Abraham On Thu, Apr 16, 2009 at 17:14, Dossy Shiobara <do...@panoptic.com> wrote: > > On 4/16/09 6:02 PM, Abraham Williams wrote: > >> the oauth_token you are returned is only good for getting an access >> token from oauth/access_token. that access token is what lets you act as >> the user. >> > > Wait, what? The oauth_token that's returned from the _oauth/authenticate_ > method is already an Access Token, for which you don't have the secret to. > > I'm hoping Twitter fixes this somehow. > > > -- > Dossy Shiobara | do...@panoptic.com | http://dossy.org/ > Panoptic Computer Network | http://panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70) > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
