So you are saying that the user of a third party application must register a completely new consumer key and consumer secret?
So when TweetDeck goes to OAuth, every user will create their own consumer key and consumer secret, therefore, having 10s of thousands of "TweetDeck" applications registered? I am talking about the user going to the site where you have to give it a name, tell twitter whether its a desktop or web application, and fill in the other information? Is that what every user is going to have to do? Sent from my DROID On Feb 9, 2010 11:53 AM, "John Meyer" <john.l.me...@gmail.com> wrote: On 2/9/2010 8:09 AM, _Bensn wrote: > > @ John Meyer - thanks for editing my post with the url. > Is ... Yeah. It might be construed as more effort than a basic authentication, but I don't believe it is that onerous. The big issue is the web interface and how it "breaks" the look of the application.
