27 ms·

I would (almost) never use a site that only allowed this as a means to login... it's so absurd that these are the only options. There should be two things they

I would (almost) never use a site that only allowed this as a means to login... it's so absurd that these are the only options. There should be two things they are interested in: 1. Is the email valid? 2. Is the credit card and details for that valid? Anything else is a distraction to making money.

stickfigure 9y ago
I would (almost) never use a site that only allowed... If you're a business customer, you'll use whatever auth system is presented. And 80% of the time Google login is perfect; the other 20% will deal. "Oh, your product will save me thousands of dollars? But it requires a Google account? Sorry, can't use it"... said nobody, ever. There's a huge difference between B2B and B2C customers, and you need to understand which business you're in. Yeah, if you're trying to accommodate the mass market, you need all the options. If you have a niche product that makes money for people, you should spend all your time working on features that make people money. Auth is not one of them.
- whatyoucantsay 9y ago
  > "Oh, your product will save me thousands of dollars? But it requires a Google account? Sorry, can't use it"... said nobody, ever. You've clearly never worked in China. All people are not living your circumstance.
TaylorAlexander 9y ago
I run a one person business and I often feel bogged down by little things. If I need auth and I can let some huge companies take care of auth for me and they’ve got simple APIs, I may choose that over some kind of roll my own. Personally I wouldn’t want to force my customers to participate in these surveillance platforms but I have also never made money on my businesses - perhaps because I put too much effort in to the little details. Edit: I also imagine fraud is costly, and if the big platforms can save me dev time on auth and reduce problems with fraud, that adds up to a significant savings.
- weaksauce 9y ago
  Fraud and auth are two orthogonal things. The only thing this does is save you from implementing a really basic login system which is really not much code to implement if you use something like devise or some other auth library. if fraud is a goal to prevent use something like paypal or stripe which is better than small shops at detecting it over some generic merchant account. All this does is tie people into one closed system identity which most people have more than one functional identity(e.g. my business identity is different than my personal identity is different than my family identity). If you force me into using facebook to login to a system where I might legitimately want to separate personal, business and family accounts you lose me as a customer. Also, you may be using some service on behalf of someone else and then what? the customer has to give you access to their facebook account? it's just shortsighted and, frankly, dumb to only allow facebook/google to control auth. use it as an additional auth mechanism if you want to but don't solely make that your only method.

stickfigure 9y ago

I would (almost) never use a site that only allowed... If you're a business customer, you'll use whatever auth system is presented. And 80% of the time Google login is perfect; the other 20% will deal. "Oh, your product will save me thousands of dollars? But it requires a Google account? Sorry, can't use it"... said nobody, ever. There's a huge difference between B2B and B2C customers, and you need to understand which business you're in. Yeah, if you're trying to accommodate the mass market, you need all the options. If you have a niche product that makes money for people, you should spend all your time working on features that make people money. Auth is not one of them.

whatyoucantsay 9y ago
> "Oh, your product will save me thousands of dollars? But it requires a Google account? Sorry, can't use it"... said nobody, ever. You've clearly never worked in China. All people are not living your circumstance.

TaylorAlexander 9y ago

I run a one person business and I often feel bogged down by little things. If I need auth and I can let some huge companies take care of auth for me and they’ve got simple APIs, I may choose that over some kind of roll my own. Personally I wouldn’t want to force my customers to participate in these surveillance platforms but I have also never made money on my businesses - perhaps because I put too much effort in to the little details. Edit: I also imagine fraud is costly, and if the big platforms can save me dev time on auth and reduce problems with fraud, that adds up to a significant savings.

weaksauce 9y ago
Fraud and auth are two orthogonal things. The only thing this does is save you from implementing a really basic login system which is really not much code to implement if you use something like devise or some other auth library. if fraud is a goal to prevent use something like paypal or stripe which is better than small shops at detecting it over some generic merchant account. All this does is tie people into one closed system identity which most people have more than one functional identity(e.g. my business identity is different than my personal identity is different than my family identity). If you force me into using facebook to login to a system where I might legitimately want to separate personal, business and family accounts you lose me as a customer. Also, you may be using some service on behalf of someone else and then what? the customer has to give you access to their facebook account? it's just shortsighted and, frankly, dumb to only allow facebook/google to control auth. use it as an additional auth mechanism if you want to but don't solely make that your only method.