3 ms·
Hmm. Problem with this approach, as with Sign in by FB/Twitter, is: what to do when the provider bans you? People have complained since years that Google takes
by mschuster91 9y ago
Hmm. Problem with this approach, as with Sign in by FB/Twitter, is: what to do when the provider bans you? People have complained since years that Google takes down their entire account including mail for stuff like "violating copyrights" on Youtube while being compliant to fair use (and then doesn't even offer you to get your data!), and Facebook and Twitter are home to troll squads abusing the "report" feature, which triggers automated anti-spam/troll systems before a human actually can do a review.
What's worse: Google, Amazon (yeah they ALSO act as a SSO provider!), Facebook and Twitter offer their users no way of appeal or even contact with a human in case of a ban, and not even when you get a lawyer to write a nasty letter to them. In contrast, regulated telcos (in Germany) have very strict requirements on when they're allowed to kick off customers. Time to regulate the giants in the same way, given their importance to not just communication across society, but also due to their growing SSO power.
- dingdongding 9y agoYou solve a problem for 99% of cases not 1% of cases
- mschuster91 9y agoTrue, but for those who do experience a ban by any major SSO provider they're straight outta luck. With FB/Twitter/Amazon SSO you can at least contact the sites you're locked out from and provide your email address to prove it's your account and hope the administrators actually have a workflow to convert a SSO-bound account to a "normal" one - but not when the only "proof" method is your mail address which is gone. I always tend to think about the 1% edge cases, because these (and the resulting bad press!) can be those with the biggest amount of time required in customer service, and in addition they're hard to set up in a way that isn't vulnerable to phishing.