3 ms·
Mozilla's Persona project solved federated ID for the Web pretty well, a decade ago. The problem is that a lot of the big tech companies want to completely own
by roca 5y ago
Mozilla's Persona project solved federated ID for the Web pretty well, a decade ago. The problem is that a lot of the big tech companies want to completely own their relationships with their users. Google is never going to let you log in with something other than a Google ID, etc. There is no technical way to solve this problem.
- cblconfederate 5y agopersona was good, but was abandoned prematurely, probably for the reasons you mention I can log in somewhere with metamask however without involving google. It's orthogonal , and that s why it can succeed
- Uehreka 5y agoOh totally true, I’m not expecting them to. I just think this could be a way to pick some of the low hanging fruit: users who want easy sign-in on sites that don’t want to roll their own IDP. Right now that niche is filled with the multicolored array of “sign in with FB, Google, MS, GitHub, Steam, LinkedIn, Apple”. This would be a way to add an extra option of “sign in with ENS” that would offer the benefit of not including tracking or any association at all with a particular company. Maybe not that many people would use it, but unlike a lot of other crypto stuff, this doesn’t require universal buy-in in order to be marginally useful to the people who do use it.
- hirsin 5y agoI mean, no, but they do let you sign in with a non Gmail address. (My @microsoft.com is a consumer Google account. Same way my @gmail personal email is a consumer Microsoft account.) Means of contact end up being a pretty useful way of organizing identities (phone numbers have their issues) and having ways to fix mistakes. The one thing I haven't seen solved in web3 is communication to a user. Easy enough to encrypt messages in ipfs though, I suppose.