4 ms·
> I’m not sure the target audience would be into this. Our philosophy is to round over the sharp edges of Web3 and make it far more accessible and safe for som
by cco 4y ago
> I’m not sure the target audience would be into this.
Our philosophy is to round over the sharp edges of Web3 and make it far more accessible and safe for somebody new to exploring the world of crypto.
> Why should I trust you with the keys to my life?
Social logins like Google or Apple offer really frictionless ways to onboard to an app that you want to use...but the data ultimately under the care and control of Google or Apple. Vessel is non-custodial, we don't own the keys, and the attestations, like verified email addresses and phone numbers, that you can choose to share with apps when you sign up are only verified by us once, after that they are held totally within your Vessel passport and you are free to share them, or not, with whatever app you'd like.
- gabereiser 4y agoBut you own the extension and the passport so really, it’s not mine, it’s yours, for the pilfering and exfiltration to other sources. A browser extension has a vast amount of data at its fingertips. Browsing history, logins, protocols, machine access, etc. You may say you’re non-custodial yet in one line of code in your close source extension, you would be custodial. I can’t trust an extension. I will not ever trust an extension. I want web3 to be accessible. I want some of the claims you make to be true. I just can’t, in good conscience, support a browser extension considering the history of security with them. I’m not alone.
- mritchie712 4y agoe.g. they could have JS in the extension sending every keystroke to their server.