Thoughts on Twitter only sign-in compared to FB? More likely to use?
Why Facebook Connect Shouldn't Be Your Only Sign-in Option
11–20 of 109 posts
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#12I never put a FB Connect button, but some people complain because they are used to logging in with one. It's a pain because it's another platform you have to support if you're a developer. What happened to the days when you just had to implement a simple website for 1 browser, without having to worry about multiple browsers, supporting iPhone, iPad, Android, and enabling Facebook/Twitter/OpenID logins, and finding fr…
There was never a day when you didn't have to worry about supporting multiple browsers.
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#13Thoughts on Twitter only sign-in compared to FB? More likely to use?
Unless your product is something that builds on Twitter's platform, I wouldn't recommend it. It means your users don't have a choice about how they're authenticated to your site, and
A) Failwhale, anyone?
B) Twitter doesn't provide serious options for protecting their users' login credentials. It's the same username/password combo which is easily phished & replayable.
Sadly, I've pretty much given up on the hope that we'll have a healthy ecosystem of OpenID providers, but at least Google's login system does offer some two-factor options.
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#14There's a good chance that if FB is the only sign-in option, I will immediately close the window and never use your service. It's pretty much an insta-bounce for me for the exact reasons cited in the article.
Has anyone run some A/B tests and gotten stats on how different subscription rates are with multiple log in options? I'm curious as to exactly how much it matters.
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#15There's a good chance that if FB is the only sign-in option, I will immediately close the window and never use your service. It's pretty much an insta-bounce for me for the exact reasons cited in the article.
I have FB blocked on my research computer from 9AM - 5PM. If I come across a site like this during the day, then I can't singn-up or login, so I usually head away quickly.
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#16I see Facebook Connect as a tool in the signup arsenal. Using it can accelerate a users signup process, but it's should still initiate a proceedure for creating a user in your own database. The user can then add Twitter and/or openID (you do support them, right?) and signin how they see fit.
However, there is a security concern. Abusing other peoples Facebook/Twitter accounts is quite common (frape for want of a better word). People do not sign out of Facebook (I don't), so blindly allowing access to sensitive data like this could be an issue. How about quickly asking for their password? Very few will be offended, and those that are should be cut down to size with an explaination of how security concious you are.
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#17There's a good chance that if FB is the only sign-in option, I will immediately close the window and never use your service. It's pretty much an insta-bounce for me for the exact reasons cited in the article.
I have FB blocked on my research computer from 9AM - 5PM. If I come across a site like this during the day, then I can't singn-up or login, so I usually head away quickly.
That's a shame. I really think IT ops should learn to trust their employees and only when that is broken, managers should decide how and when it is appropriate to block such sites.
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#18I wonder if browserid[1] is a better alternative. It doesn't require a Facebook account or anything like that and is actually surprisingly easy to use (from the user's point of view). I only tried the demo, but it was basically frictionless.
[1]: https://browserid.org/about
I haven't evaluated it completely, but it seems like the best option right now.
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#19Twitter vs. Facebook as the only options. It's as if OpenID never existed. Which, sadly, may be nearly true.
Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option
#20The article has many valid points, but the Topsy example is simply poor execution on their part to request so many extended permissions as part of the initial login authorization dialog.
Any Facebook authorization dialog that asks for all of those permissions in the Topsy example is doing it wrong. It is not like you need to ask for all of those permissions up front. Offline access and publish stream is a very dangerous combination and should only be requested when a user is turning on a feature within the app that requires them. Let the user in with the bare minimum of permissions (user_about_me), build their trust, and then only ask for more permissions as and when they are needed.
Plus when you cancel out of the Facebook authorization dialog on Topsy, you get a 500 error response. Topsy fail on multiple levels.