@ John Meyer - thanks for editing my post with the url.
Is it right, every user who wants to use our application must at first
register the application?

On 9 Feb., 11:24, _Bensn <benjaminroh...@t-online.de> wrote:
> Where can they create there own keys? here -https://twitter.com/apps/new
> ?
>
> On 8 Feb., 18:55, John Meyer <john.l.me...@gmail.com> wrote:
>
>
>
> > On 2/8/2010 7:25 AM, _Bensn wrote:
>
> > > Hi there,
>
> > > is it possible to develope a twitter application which uses oauth and
> > > it can be used by more different users without that every user musst
> > > create the customer key and -secret?
> > > we want to develope a own twitter application with own api, and we
> > > also want to set the "from ["MY_APP"] parameter. But we also want that
> > > every user can use this application, without long authentication
> > > proceses.
>
> > > Best regards,
>
> > > Benjamin
>
> > Well, technically they aren't creating the customer keys (public and
> > secret).  Those are yours.  What they're creating are their own oAuth
> > keys (public and secret).  But I'm assuming you have your terms mixed
> > up.  What you need to do is create several different profiles (i.e. sets
> > of different oAuth keys) and store them somewhere in the computer.
> > Registry, ini keys, database, cookies, where-ever.  Then you load those
> > up.  So multiple users (technically user accounts) can use the same
> > account.  How you secure those is up to you.  And the authentication
> > process really isn't that long when you get down to it.- Zitierten Text 
> > ausblenden -
>
> - Zitierten Text anzeigen -

Reply via email to