41–50 of 319 posts
Are there any security risks with signing onto a site with Metamask? Is there any way for them to drain your wallet without prompting you? If not, then it seems to be a superior method and experience. You don't have to deal with usernames/email/password, and it offers more functionality with currency.
Several years ago, Mozilla/Firefox created "Persona," which was an open-source federated identity system that provided all the benefits described here. The idea was that it would eventually be built into browsers. I used it on a commercial site myself for many years. It failed to gain traction, and Mozilla eventually pulled the plug. Persona had many advantages over the Web3 vision described in this article. It was p…
federated systems are bad, they combine the negatives of centralized and decentralized systems it is no wonder that they fail repeatedly
Are there any security risks with signing onto a site with Metamask? Is there any way for them to drain your wallet without prompting you? If not, then it seems to be a superior method and experience. You don't have to deal with usernames/email/password, and it offers more functionality with currency.
The only way anyone can gain control of your wallet is if you give them your private key (or the seed to the privk) or if your PC is compromised (but you have bigger issues then)
Why can't this be done with existing public key cryptography?
My question with any blockchain application is always what does it solve that a centralized trusted database doesn't solve faster and with less waste? You can implement social recovery in a centralized database with less waste.
Most web2 apps supports a smaller number of SSO providers. Technically "independent" SSO providers and similar existed, but non made it mainstream because there was no reason for App's to support them, but there was cost to support them. There is even less reason IMHO for most App's to support Web3 login (more complexity). Furthermore even if they do the web3 login would probably still list Google etc. as the web2 lo…
You don't really need a blockchain unless you need to keep data on a blockchain. To login and identify a user you can simply sign a message. I consider the address as the user "identity". Any blockchain data related to that address is mean to be public (some people register .eth on the ENS for example)
Several years ago, Mozilla/Firefox created "Persona," which was an open-source federated identity system that provided all the benefits described here. The idea was that it would eventually be built into browsers. I used it on a commercial site myself for many years. It failed to gain traction, and Mozilla eventually pulled the plug. Persona had many advantages over the Web3 vision described in this article. It was p…
Looking back, I now see that not volunteering myself for the challenge was one of the biggest mistakes I've made in my career. It was one of those rare opportunities to make a difference.
I also wonder why nobody has tried it since. It's a simple approach, but you'd need a good security team backed by a trusted organization to make an implementation credible.
This is progress?
>Every Git clone is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server...
http://web.archive.org/web/20080821113906/http://git-scm.com...
Sure git can be used without the need to have have a central server, but everything became so much simpler with github and other code repositories.
Decentralized systems are hard to navigate and humans will choose the easy thing every time.