4 ms·

Very good point. I've got plans to add "use it now, sign up later" stuff in, it's just not made it into production yet.

• anonymous236 16y ago
  Yep, needing to use Twitter account for login is a major minus. Maybe I am too old-fashioned, but if I click on Sign-In and it automatically logs me in, this is more of "WTF has just happened and where did it get my login credentials?" rather than "Ohhh, very cooooool, dude. Just saved 5 seconds and not needed to press 20 (twenty!!) keys. Awesome.".
  • kylebragger 16y ago
    This is actually refreshing to hear; I'm usually used to seeing the exact opposite - "what do you mean another account?!?". I wonder if adding an interstitial page with something to the effect of "you're signing up with Twitter FYI" would be a decent intermediary step.
    • zalzally 16y ago
      Good idea, Kyle. I don't mind Twitter or Facebook OAuth logins for non-sensitive consumer apps (sensitive = apps dealing with financial info, dating sites, health, etc.). Just tell me upfront that you're using the service, and I'll be happy that I don't need to create a new account.
      • kylebragger 16y ago
        Great point. I'm going to make it a top priority.
    • tomjen3 16y ago
      Thats because those people haven't reduced the friction to create an account yet - I have it down to about 20 seconds and making the browser remember the password means it is actually faster from then on. If you absolutely must, then use OpenId. It is was pretty much made for that (and it works with twitter, facebook, gmail, your mom, etc).