<oembed><type>rich</type><version>1.0</version><title>zach wrote</title><author_name>zach (npub1za…m5dy5)</author_name><author_url>https://yabu.me/npub1zach44xjpc4yyhx6pgse2cj2pf98838kja03dv2e8ly8lfr094vqvm5dy5</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>I think this leaves us with 2 options.&#xA;&#xA;Either A) We educate new users about the basics of Nostr, to get them aqcuatented with key managment and how things will work.&#xA;&#xA;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. &#xA;&#xA;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 &#xA;&#34;Opt-out&#34; 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.</html></oembed>