On 4/16/09 2:37 PM, Abraham Williams wrote:
I'm not quite sure what you mean by this. Oauth/authenticate works pretty much exactly the same as oauth/authorize but uses a different path and may not require any action by the user if they have previously authorized.
How do you know which oauth_token to supply to Twitter when making the request? You maintain your own username/password database for your users that you then associate to their oauth_token's?
My hope was that we could leverage Twitter to authenticate (!) users so that we third-party app. developers wouldn't need to authenticate users separately with our own user/password scheme.
One can dream, right? :-) -- Dossy Shiobara | [email protected] | 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)
