Real Problems That Web3 Solves, Part 1
billprin.com
Real Problems That Web3 Solves, Part 1
1–10 of 319 posts
Re: Real Problems That Web3 Solves, Part 1
#2No post body was provided.
Re: Real Problems That Web3 Solves, Part 1
#3Great post!
This definitely has me thinking more about the extent to which the strength of a particular identity representation is determined by our willingness to bind artifacts of value to it.
Re: Real Problems That Web3 Solves, Part 1
#4I like the starting focus on identity. Imagine if emails to you were authenticated by a token that you authorized by logging in, and could revoke at any time. In a Web2 world, features like this get created by Google, Apple or whomever inventing a permissions system that works on their platform -- and serves their product goals. In a Web3 world where you issue identity tokens, you can revoke them arbitrarily, so if your identity is shared you can trace and revoke at the root. Services move from worrying about how to game Apple's privacy model to how to avoid a ban that remains strictly in your control.
Re: Real Problems That Web3 Solves, Part 1
#5My big question with using a Web3 login is what advantages it gives the website owner.
With social Web 2.0 login, I can be fairly sure the person logging in has a valid email address, a name, etc, and it is a single click for the user vs filling in all the info all over again.
With a Web3 login, it is basically the same. Except I'm not really given any personal info like name or email, so I need ask them for that anyway. I guess you can tie that into your wallet somehow?
But I don't see this as a 10x solution. Do people really not trust FB/Google/Twitter that much? Why does currency and money need to get involved?
But in another world, isn't this the problem Keybase was trying to solve? Of course, they got mixed up in their own cryptocurrency as well (XLM) which had so many issues with bots trying to get into the airdrop. So idk.
Re: Real Problems That Web3 Solves, Part 1
#6My big question with using a Web3 login is what advantages it gives the website owner. With social Web 2.0 login, I can be fairly sure the person logging in has a valid email address, a name, etc, and it is a single click for the user vs filling in all the info all over again. With a Web3 login, it is basically the same. Except I'm not really given any personal info like name or email, so I need ask them for that any…
Web3 emphasizes privacy be default. Emails are no longer needed for password management so if u need them for something else users should opt-in.
Re: Real Problems That Web3 Solves, Part 1
#7I suppose blockchain can be a mechanism for the reification of pure information. So turning something that only has a value, into something that has a unique identity that can be 'pointed to'.
In the real world I might have a physical key (or some other interesting object) - there is exactly one of it and it exists in exactly one place (though of course I can create copies - but they are new objects).
In the virtual world this is a bit harder to construct and enforce - information is entirely ephemeral, and has no concrete existence or place. Maybe blockchain can provide that (in the context of the chain only of course).
Re: Real Problems That Web3 Solves, Part 1
#8Most 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 login still lists email.
It's questionable that more than one maybe two blockchains will be supported.
It's likely that often only a small number of wallets will be supported, it's also likely that "bigtech" companies like google will provide web3 logins if it becomes successful.
So, it might happen. But I don't see it tbh.
There is just no reason to go the extra length to support web3 login for most Apps/Companies.
EDIT: Also trust of the general public into anything containing the word "crypto" or "blockchain" is constantly undermined by an endless slew of scams, and money grabbing schemes. Which can hurt adoption of web3 login.
Re: Real Problems That Web3 Solves, Part 1
#9My big question with using a Web3 login is what advantages it gives the website owner. With social Web 2.0 login, I can be fairly sure the person logging in has a valid email address, a name, etc, and it is a single click for the user vs filling in all the info all over again. With a Web3 login, it is basically the same. Except I'm not really given any personal info like name or email, so I need ask them for that any…
>Do people really not trust FB/Google/Twitter that much?
People in general or HN audience?
Re: Real Problems That Web3 Solves, Part 1
#10Quoted post unavailable.
[deleted]