3 ms·
That's a very quick depreciation timeline... Do you think this feature has some unfixable security issue? Or perhaps there are only a handful of users?
by londons_explore 5y ago
That's a very quick depreciation timeline...
Do you think this feature has some unfixable security issue?
Or perhaps there are only a handful of users?
- toomuchtodo 5y agoIt looks like Facebook is the partner used and there might be motivation to move away from using them as a partner for identity proofing as part of the identity operation (where as Github could use someone like Stripe Identity instead, with the cost being ~$2 per proofing request [1]). Tangentially, I support anyone moving away from Facebook for identity purposes. [1] https://stripe.com/identity https://stripe.com/identity
- jsnell 5y agoBut this was not a use case that was using proof of real-world identity. How could that service possibly be relevant in any way? In fact, Github would know nothing about the identity of the Facebook account (and vice versa). This connection would be completely anonymous from both their perspectives. All Github could find out is is that somebody trying to recover the account had access to the preregistered (but unknown) Facebook account. And all Facebook would find out is that a user was recovering some unknown Github account.
- toomuchtodo 5y agoThere are many paths to account recovery, and using real world identity as the cost comes down is a legitimate path forward versus "Facebook identity."