lucas on Nostr: If we want #Nostr to reach mass adoption, we may need to lower the barrier of entry ...
If we want #Nostr to reach mass adoption, we may need to lower the barrier of entry for less technically inclined people. Perhaps, a greater emphasis on the "Nostr Address" and less on the npub? Similarly to how the json event is hidden, but if you really want to find it, some clients will show the payload. Something like that to conceal the pubkey and have folks primarily utilize the nostr address to find people, etc. What that looks like entirely, I'm not too sure, but maybe it requires some clients supporting various Nostr address creator's API (or their own) to generate someone's address upon sign up.
Published at
2024-04-05 21:51:48Event JSON
{
"id": "233f89330b1264818aa3f635945c2c97926360340190a832507e089b2266158d",
"pubkey": "d49a9023a21dba1b3c8306ca369bf3243d8b44b8f0b6d1196607f7b0990fa8df",
"created_at": 1712353908,
"kind": 1,
"tags": [
[
"t",
"Nostr"
],
[
"t",
"nostr"
]
],
"content": "If we want #Nostr to reach mass adoption, we may need to lower the barrier of entry for less technically inclined people. Perhaps, a greater emphasis on the \"Nostr Address\" and less on the npub? Similarly to how the json event is hidden, but if you really want to find it, some clients will show the payload. Something like that to conceal the pubkey and have folks primarily utilize the nostr address to find people, etc. What that looks like entirely, I'm not too sure, but maybe it requires some clients supporting various Nostr address creator's API (or their own) to generate someone's address upon sign up.",
"sig": "fba2e92abd46782a57dde510186b268df630037e17ab0467652dcdb6a326eb60e1c2577bded046b84321cc53d6def9c5063e6ec3e72faa00728462e9d2a84bab"
}