Nostr Web Client

The comments on https://news.ycombinator.com/item?id=38718544 are proof that we can't make "just apps" and have people use them without knowing that Nostr is a thing. Users must know.

And in fact I think it is much easier to teach people about Nostr than about why your damn app doesn't have email+password login and where is it storing things and how does moderation work without telling them about Nostr.

And when they finally understand the basics of Nostr they will suddenly understand everything about not only your app, but about all other Nostr clients.

Zach 2y ago

I think this leaves us with 2 options.

Either A) We educate new users about the basics of Nostr, to get them aqcuatented with key managment and how things will work.

B) We abstract away as much as we can initially so users just think they are using a normal web app until they leter realize what makes Nostr different.

I think that route B is easier for board adoption, but, it will be very important to build things in such a way so users can

"Opt-out" of custodial key managment solutions once they have spent the time to get a better understanding of how nostr works. What nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft has been working on will help onboarding immensely imo.

Reply to this note

Please Login to reply.

Discussion

freed0m 2y ago

How to handle key management on mobile, other than:

- nsecbunker (buggy)

- installing a new browser and an extension (ux black hole)

Genuinely curious what the options are

fiatjaf 2y ago

Try Amber.

I wish Amber had a "default reject" policy though so I can prevent Amethyst from using it to decrypt things and whatnot.