Ok, great. I'll let it check, so.
By the way, OAuth is working like a charm here. Great job you did
there! I'm happy to have finally switched to it.

All the best,

On Jul 1, 4:50 pm, Matt Sanford <m...@twitter.com> wrote:
> Hi Arnaud,
>      That option during application creation is really more trouble  
> that it is worth. Right now applications that have that option checked  
> include an extra sentence to tell users the application will be using  
> twitter for login, that's all. In the future we may restrict the /
> oauth/authenticate call to applications that have specifically chosen  
> the option, so I recommend that any application using 'Sing in with  
> Twitter' check the check box. We're also working on redesigning the  
> authorization page and might do more with that value then.
>      We will announce before hand if we make any changes, like  
> requiring that value to use the authenticate method. It's not  
> something we'll definitely do but it is something that may come up in  
> the medium term you should be aware of.
> Thanks;
>   – Matt Sanford / @mzsanford
>       Twitter Dev
> On Jul 1, 2009, at 4:26 AM, Arnaud wrote:
> > Hello,
> > I’m using the oauth/authenticate method (one click login) and I was
> > wondering if I had to check the "Use Twitter for login" option in my
> > application options. The application is Browser based (using a
> > callback URL) .
> > I’m quite confused with this option as I don’t really understand what
> > it is standing for?
> > All the best,
> > Arnaud.

Reply via email to