Ethan Jewett wrote: > 1. The user authorized TwitPic to access Twitter (OAuth dance #1). > 2. The user authorizes TweetDeck to use the TwitPic API (OAuth dance #2).
It seems like this could actually be made to look like a single "dance": * User of TweetDeck requests a connection to TwitPic. * TwitPic asks the user to log in. * TwitPic checks if it already has a Twitter OAuth access token for this user. If it does, it skips the next step. * TwitPic initiates an OAuth dance with Twitter to get a Twitter access token. * TwitPic issues an OAuth access token connected to the TwitPic account, which is indirectly connected to the Twitter account. So the user sees TweetDeck -> TwitPic -> Twitter -> TweetDeck in the initial bootstrap case. This is likely to make the user a little confused, but perhaps the TwitPic UI can say something like "Before <application name> can use TwitPic, we must connect to your Twitter account." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
