YourHead Software

On Jul 1, 2009, at 10:23 AM, Matt Sanford wrote:

Hi there,

   A mobile version does not exist but it's on the roadmap.

— Matt

On Jul 1, 2009, at 10:21 AM, Isaiah Carew wrote:

I'm still not sure I understand the option. Is there any reason why someone would choose NOT to check this box currently?

Also, if you are in the process of redesigning the auth page, could I make a request: Could there be a super-lightweight version for mobile? No images, no scripts, inline css, fluid width, etc.

Maybe it already exists and I'm doing something wrong. Feel free to point me in the right direction too. ;-)


On Jul 1, 2009, at 7:50 AM, Matt Sanford 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.

– Matt Sanford / @mzsanford
   Twitter Dev

On Jul 1, 2009, at 4:26 AM, Arnaud wrote:


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,

Reply via email to