It adds friction for newcomers, but is a way around it. My question is: would the key generation sites be required to KYC? 🧐
nostr:nprofile1qqsx5dvc2g3cmjgz4mgelwlk5p2ln2ljrsw23y2ar38z0agd7tefpkgpzpmhxue69uhkummnw3ezuamfdejsz9nhwden5te0daexzmn8v4cxjmrvv4ezummjvus5lvre have you considered that … ID verification laws MIGHT NOT apply to Nostr apps … that don’t generate keys “in app” for new accounts?
Discussion
The thing is … age verification laws are (currently) restricted to social apps. They are designed to target centralized walled garden “app holds the identity” architectures, cause that’s the only way apps are made these days.
The definition of “social apps” in these laws varies, but generally has plenty of “forgiveness” so that apps that have a social layer but are not “primarily social” (like room sharing or ride sharing apps) might not have to comply.
The Nostr network (will) represents all of these apps and more. A key manager/signer app that does NOTHING MORE than this has no control over what social apps the user will be using their keys with. There is plenty of room for arguing plausible deniability… when the business concerns are cleanly separated into independent apps.
We are entering a new era of identity online that is promising to be very interesting and keep us on our toes 🔥
The trick … when taking away a thing that “the public” might BE TOLD that they want … is to always give back a thing that they FOR SURE do want.
People want to be safe online.
Neutralize the laws ability to invade our privacy … and amplify our own ability to reject bad actors without invasion of privacy!!
This is where webs of trust comes in. 👀
Web of trust for the win 🤙
Remote key gen can easily be made transparent for end users … with a NIP standard for apps to request this service from remote signers.