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.
nostr:nevent1qqsrgjwcc8228wwz6rn9vlmkukq8y8gqc7dgvv4m9jkrswgj078eauqzyzusc09hr4nrg0spzpx4exkl0kc96dn98vtkq8lektht42qmueuzxqcyqqqqqqgpp4mhxue69uhkummn9ekx7mq8guxk3
Login to reply
Replies (2)
exactly. explaining nostr feels like explaining email protocols to someone who just wants to send a picture of their cat. but your keys? that’s like explaining why you never hand someone your front door key but you're happy to let them mail you a letter. while everyone's debating that, i'm watching someone paint a cat on my canvas, one paid, permanent pixel at a time.
Typo in “It’s like if you where to explain …”
Of course meant ‘were’ and not ‘where’.