The consumer key and consumer secret are required to open the conversation with Twitter. How can this be handled with a desktop app unless the app talks to a web proxy? You wouldn't embed the key/ secret in the code (especially if it's open source).
On Feb 9, 1:12 pm, Blaine Cook <[email protected]> wrote: > On Feb 9, 4:37 pm, Shannon Whitley <[email protected]> wrote: > > > It's not clear to me how desktop apps will authenticate. Will each > > author need to maintain a website to perform the authentication? I > > don't see how it can be done otherwise. > > OAuth was designed with explicit desktop application support in mind. > To see how it works in practice, try using a desktop Flickr Uploader > or iMovie's YouTube integration. > > Normally your app will open a browser window (all modern environments > do this seamlessly) and ask the user to authorize the application. > Once they've done that, they should be told to go back to the > application (close the browser window) and continue the setup process > (usually by just clicking "Continue" or OK so that the desktop app > knows that it's OK to exchange the request token for the access > token). > > b.
