Live data from Hacker News

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

bijansabet.com

81–90 of 109 posts

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

#81
post #38

Earlier quoted context omitted.

Given that there are ~ 300M americans and facebook has ~850M users, my guess is that most of their userbase is overseas (and oftentimes falling prey to the whole "americans use it, so I should also be using it" mentality)

For a long time Facebook wasn't available over seas. Facebook started with only US colleges, then high schools. It only opened up to people outside the US about 3 years ago I think so I would assume a large percentage of its user base is american.

False, Facebook was getting popular in my uni in the UK back in 2003.

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

#82
post #67

As much as I love Khan Academy, I hate, that they only offer Facebook and Google as sign-in options. I try to avoid both of them as much as possible.

Would you prefer Twitter or something else? Or do you want a site-specific sign-in?

Site specific signup, any day, with long lived cookie remember me. Way too many companies view my FB credentials as a way to market themselves to my friends rather than as a convenience to me.

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

#83
post #38
post #35

Earlier quoted context omitted.

I don't, my parents, grandparents, aunts and uncles don't, my best friend doesn't, several of my favorite past and present colleagues don't. There are times I really wonder where Facebook's massive userbase comes from, and how it can ever possibly occur to anyone, anywhere, under any circumstances, to make Facebook the sole login system for their web startup that otherwise has little or nothing to do with Facebook.

Given that there are ~ 300M americans and facebook has ~850M users, my guess is that most of their userbase is overseas (and oftentimes falling prey to the whole "americans use it, so I should also be using it" mentality)

> (and oftentimes falling prey to the whole "americans use it, so I should also be using it" mentality)

That's a pretty low option of foreigners; in practice I think they take which bits of American culture they like, adapt it if necessary and ignore the rest. I would guess most of FB's non-USA users use it for the same reason USA-users do; its good at what it does, and all their friends use it.

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

#84

Twitter vs. Facebook as the only options. It's as if OpenID never existed. Which, sadly, may be nearly true.

Outside the world of programmers and StackOverflow, I can't think of a single site. Kudos to them for at least trying to solve this problem tho.

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

#85
post #18

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

Really like that idea. Would love to see more sites implement it.

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

#86
post #82
post #67

Earlier quoted context omitted.

Would you prefer Twitter or something else? Or do you want a site-specific sign-in?

Site specific signup, any day, with long lived cookie remember me. Way too many companies view my FB credentials as a way to market themselves to my friends rather than as a convenience to me.

+1 Personally I find the whole idea of relying on a third party site for sign-in a bit odd. Let it be Twitter, Google, Facebook or anything else... there will always be people, who don't have an account for that specific site, don't want one, or don't want to let the site's owner know what their name on that third party site is. Another problem: aren't Google and Facebook blocked in some countries like china? Again, the whole idea doesn't work out in my opinion.

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

#87

Earlier quoted context omitted.

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

He actually said that he had it blocked - that could easily be read to mean that he blocked it or someone else blocked it.

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

#88

Thoughts on Twitter only sign-in compared to FB? More likely to use?

For me, neither. I've got no interest in linking my identity in one online service to my identity in a totally unrelated one.

I've just signed up for a free trial to Netflix and they seem to be determined to force you to link its account to your Facebook one (you can avoid it by signing out of FB before going on the Netflix site, but even if you do that it then attempts to link the two together in the background next time you go on the Netflix page). But I don't want my FB page filling up with a list of things that I've watched. Partly because I may sometimes want to watch something I don't want to broadcast to the entire world, but mostly because I doubt that most of my friends have the slightest interest in keeping track of my everyday viewing habits.

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

#89

There'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.

And I live in China and don't have a proxy. At least let me use Google or Yahoo or something.

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

#90
post #72

This post reminded me to look for open source code to handle multi-logins, I'm currently in the planning stage of a project. These seem quite comprehensive. Is there any reason why I would be better off rolling my own code? http://www.omniauth.org (Ruby/Rack) https://github.com/bnoguchi/everyauth (node.js) https://github.com/ciaranj/connect-auth (node.js)

If you actually need to use the user's Facebook information I suggest you use Koala and the JS login flow, otherwise omniauth is a good solution.

On the node.js side - just look at everyauth and connect-auth examples - they didn't even work on my computer! there's another lesser known library called passport.js that does the job very well: http://passportjs.org/

Post reply on HN