3 ms·
I'm the author of the article. I agree that looking at the title today, it is misleading. I wrote that as a case study of an experiment we did at Visible. I thi
by karellm 9y ago
I'm the author of the article. I agree that looking at the title today, it is misleading. I wrote that as a case study of an experiment we did at Visible. I think it is important to keep that in mind, I do not pretend it is THE flow to use or that it makes sense for other websites. We were trying different things to reduce the friction when onboarding users.
I agree with social login, except that I personally traded the convenience for privacy. Most website grab way too much data and as a result I rarely use social login. And in the realm of enterprise Sass I think it is a fair concern to have; Security is taken more seriously. That said, it doesn't mean that we could have implemented social logins without grabbing unnecessary data!
- nkkollaw 9y ago> I personally traded the convenience for privacy You can choose what to do with the data. I assume you trust yourself to save only what you need (even just the social network ID if you really want to?) > Security is taken more seriously I trust Facebook to keep my password safe more than a random website I know little or nothing about (not yours, any website), if anything because Facebook has 100 times more resources than most other services. Also, most people use the same password for everything, the less places it's stored, the better. :-)