Ah, ok.
i think i understand it now... ;-) thanks!

On 10 Feb., 16:12, ryan alford <ryanalford...@gmail.com> wrote:
> The user doesn't actually "create" their OAuth tokens manually.  The tokens
> are created automatically by Twitter and given to you through responses
> after the user has given your application permission to their account.
>
> Ryan
>
>
>
> On Wed, Feb 10, 2010 at 8:27 AM, _Bensn <benjaminroh...@t-online.de> wrote:
> > And where get the users there own keys to use the application with
> > there own twitter account? (e.g tweet deck)
>
> > On 9 Feb., 18:29, John Meyer <john.l.me...@gmail.com> wrote:
> > > On 2/9/2010 10:03 AM, ryan alford wrote:
>
> > > > So you are saying that the user of a third party application must
> > > > register a completely new consumer key and consumer secret?
>
> > > Again, you have your terminology wrong.  They get a completely new set
> > > of oAuth tokens.  Same as the fact that every user of twitter has to
> > > register his or her own Twitter username/password
>
> > > > 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?
>
> > > No.  One TweetDeck application is registered.  Those users have just
> > > authorized TweetDeck to access their application.- Zitierten Text 
> > > ausblenden -
>
> - Zitierten Text anzeigen -

Reply via email to