Live data from Hacker News

Why Facebook Connect Shouldn't Be Your Only Sign-in Option

bijansabet.com

21–30 of 109 posts

Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option

#21
post #12

I 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.

when IE was 95% market share?

Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option

#22
The services who use Facebook always annoy me with sharing requests, i don't want to share anything stop asking. When somebody who uses Facebook Connect only, i expect this in advance and often don't want to use the service at all.

With Google Login i never get those.

Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option

#23
The Facebook connect image is somewhat misleading. Sure, using FB connect can involve a screen like that, but you can also present a simple screen that only asks to "Access my basic information". Not nearly as confusing, doesn't raise questions about surreptitious posting. You can ask your customer for more access later, after you've earned trust in your relationship.

Further, some customer bases are perfectly happy using FB connect only. If you object to logging in with Facebook, maybe you're just realizing that you're not the target market for the product. No harm, no foul. If you end up offering lots of log-in options and your customer base only really wants FB, you waste development time and actually run the risk of confusing your customers.

Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option

#24

Earlier quoted context omitted.

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.

He said, he blocks it, no the IT ops

Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option

#25
While I agree with the point that FB Connect should not be the only option, I don't see promoting password-based authentication is beneficial here. Implementing a traditional user&pass auth. scheme:

1) Is really hard to get right from the security standpoint ( https://www.owasp.org/index.php/Authentication_Cheat_Sheet )

2) Actually requires quite significant work. It might be easy to add short sign-up and login forms to a site, but I doubt that implementing any external authentication mechanism would be really that much more work. However, with password auth. the work doesn't end here. We typically need password reset/recovery and password change. The latter usually entails some kind of profile/settings page, while the former might require at least a dedicated login page.

In general, external authentication providers are good, as long as we don't limit ourselves to a single one. Adding Twitter / Google / BrowserID / Open ID / etc. is not that much more work, as the whole flow can be somewhat generalized. Having multiple authentication options also makes us prepared (from implementation PoV) for eventual support of user&pass auth., should we need it in the future.

Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option

#26
From user perspective having several sign-in options is a source of confusion: first day I sign in with Facebook... next day I come in and don't remember which service I've used to sign in with? And this time I try Twitter only to see none of my data.

How do you guys solve that problem? I think, this might be even the bigger problem than having 20% or 30% "drop out" on sign up process.

Re: Why Facebook Connect Shouldn't Be Your Only Sign-in Option

#28

From user perspective having several sign-in options is a source of confusion: first day I sign in with Facebook... next day I come in and don't remember which service I've used to sign in with? And this time I try Twitter only to see none of my data. How do you guys solve that problem? I think, this might be even the bigger problem than having 20% or 30% "drop out" on sign up process.

You'll probably see that you don't have an account registered with the website through Twitter, not "none of my data". As a user, if you like FB more, you'll likely try FB login first. If you like Twitter more, you'll likely try Twitter login first (if available).
Post reply on HN