3 ms·

For a website, I offered login with Twitter, Facebook or custom username/password. I thought people would take the easy way, and use their FB login. Wrong! 90%

by jusob 16y ago

For a website, I offered login with Twitter, Facebook or custom username/password. I thought people would take the easy way, and use their FB login. Wrong! 90% of them chose the custom login + password.

udfalkso 16y ago
I'm curious what your audience was like. Young? Old? Tech Savvy? Did your site focus on something potentially embarrassing if it would end up on your FB profile?
- jlgosse 16y ago
  From my experience the average internet user is quite afraid to give up their Facebook credentials to a random site.
  - _delirium 16y ago
    Yeah, I think FB Connect hits right at the time that anti-phishing education has finally made people super wary of cross-site types of issues. They've had repeatedly banged into their heads: if the URL bar doesn't say example.com, don't give any of your example.com-related information to it, no matter what story it tells you! Of course, FB Connect doesn't actually require you to enter your Facebook password into a non-Facebook site, but I can see how people would be scared off. Using your Facebook credentials for something you didn't reach by typing facebook.com into the URL bar yourself feels at least superficially just like the sort of thing all these campaigns have been about...
tomjen3 16y ago
What was your reason for not just using openid? It is a standard, gets you a wider user base and the services already mentioned support it too.
- sqrt17 16y ago
  Most people who would have an OpenID-supported authentication method wouldn't know that they do or how to use it. A big "use Facebook/Google/Gravatar/whatever to log in" button makes it easy even for the people who don't have any OpenID background.
  - jusob 16y ago
    Exactly. Even I feel using Open ID is quite complicate when I was forced to use it for the first time on Stackoverflow.
metachris 16y ago
I'm building http://flockengine.com http://flockengine.com, a multiplayer framework in beta (currently with Android client). About 30% of players choose to sign in via Facebook, 70% prefer to create a custom account.

by jusob 16y ago

udfalkso 16y ago

I'm curious what your audience was like. Young? Old? Tech Savvy? Did your site focus on something potentially embarrassing if it would end up on your FB profile?

jlgosse 16y ago
From my experience the average internet user is quite afraid to give up their Facebook credentials to a random site.
- _delirium 16y ago
  Yeah, I think FB Connect hits right at the time that anti-phishing education has finally made people super wary of cross-site types of issues. They've had repeatedly banged into their heads: if the URL bar doesn't say example.com, don't give any of your example.com-related information to it, no matter what story it tells you! Of course, FB Connect doesn't actually require you to enter your Facebook password into a non-Facebook site, but I can see how people would be scared off. Using your Facebook credentials for something you didn't reach by typing facebook.com into the URL bar yourself feels at least superficially just like the sort of thing all these campaigns have been about...

tomjen3 16y ago

What was your reason for not just using openid? It is a standard, gets you a wider user base and the services already mentioned support it too.

sqrt17 16y ago
Most people who would have an OpenID-supported authentication method wouldn't know that they do or how to use it. A big "use Facebook/Google/Gravatar/whatever to log in" button makes it easy even for the people who don't have any OpenID background.
- jusob 16y ago
  Exactly. Even I feel using Open ID is quite complicate when I was forced to use it for the first time on Stackoverflow.

metachris 16y ago

I'm building http://flockengine.com http://flockengine.com, a multiplayer framework in beta (currently with Android client). About 30% of players choose to sign in via Facebook, 70% prefer to create a custom account.