Explaining what #Nostr is and the parts that make up Nostr in a non-technical way is difficult. It’s like if you where to explain to normies what email is and what it can do. Everyone knows what email is, but no one really knows it on a technical-level except for devs. Ask a normie what SMTP is and they wouldn’t know, and it’s fine, because they shouldn’t need to know.
Likewise, people don’t need to know about NIPs. But very fundamental parts of Nostr that have direct impact on how the user interacts with Nostr are unavoidable for people to understand. Keypair is one example. People need to understand the use of the npub and nsec and how they should manage these (like never sharing the nsec to anyone).
Maybe relay, but you can use Nostr without ever worrying about relays - depends on the specific client though.
For starters there's the assumption that you can use the following words with normies;
-Protocol
-Relay
-Bunker
-NIP
-Keypair
-Secret
-Signature
-JSON
-Event
-Auth
You just cannot. You can get away with introducing maybe one easy-to-grasp concept, like how Snapchat came up with Stories, but that's it. (Maybe there's some very lightweight way to present relays that doesn't include the word relays.) The rest you have to abstract away more or less completely, and once done so the experience has to speak for itself.
Nostr is so dev-heavy right now.
View quoted note →
