4 ms·
Wait, let me get this straight - your company has the non-sharded encryption key (not the user), it centralized by your service, and all of that is subject to g
by officialchicken 5y ago
Wait, let me get this straight - your company has the non-sharded encryption key (not the user), it centralized by your service, and all of that is subject to google's whims. Yep, sounds like the heart of web3.
- evv 5y agoMetamask is distributed through Google as well, and it operates in Chrome. It would be easier to let me know what web3 technology is not subject to Google's whims!
- officialchicken 5y agoI dunno, say, Brave browser??? Just spitballing here.
- cyberge99 5y agoIPFS
- Spivak 5y agoIf you want something to have broad appeal you have to hide the key management. Users will never keep track of keys or wallets and they will lose them regularly. Most services solve this by not having the key be the source of truth for anything (i.e. iMessage, WhatsApp, and SSH) so that you can rotate them on a whim. Other services solve this by just hosting the key when it's actually important (Bitlocker). This is just an example of the latter. Sites that support "Login with Google/FB/Email" aren't some malicious conspiracy theory, they're how most people access and secure all their information.