[jasonkester]

You forget though that you've studied all this stuff. Casual users of your thing won't have.

So when you say "Give me your Twitter username and password", they'll say no. It doesn't matter that it's actually safe. It certainly doesn't sound safe, and that's all that matters.

Argue against it at your own peril. People are comfortable with user/pass.

[dannyr]

I'll argue to the contrary.

Lots of sites use Facebook Connect because it actually drives signups.

Where are you basing your argument that people do not actually want to give their twitter username and password?

In my experience, a lot of casual users do not actually care. We had an email inviter that was used frequently where people actually have to give out their Gmail/Yahoo/Hotmail credentials.

You may be comfortable with user/pass but do not make the assumption that the rest of the world are. You may think you're mainstream but you're probably not.

[bryne]

You're blowing up a straw man. Quite a few people may actually have an active Twitter session and thus no active password entry even occurs. Open it up to Facebook Connect and it's more of the same.

You're comfortable with new user/pass and it doesn't sound safe to you.

[keithpitt]

I see what you guys mean. Hopefully when we can add features agin we'll able to implement these things. We had FB connect, but took it out because we didnt have time to test it enough. We also took out username/password auth because we felt it would complicate things - perhaps not?