SHOUT OUT to nostr:nprofile1qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qy88wumn8ghj7mn0wvhxcmmv9uqzqp5fmavy02xnxa5f9k3fvgkhcr7urmcetr6tc3r3myykd2s7e20jfgn7gs for responding to this #asknostr appeal. Thanks, Friend!๐Ÿ™๐Ÿป๐Ÿซ‚๐Ÿ˜€

I was really floundering on this... And I have a couple of comments to share for whomever may care to listen.

I have been wanting for some time to have secure access to a web-based client so that I can use a full-sized keyboard for typing/data entry. I've hesitated due to not having an "nsec bunker" setup.

I've worked with computers most of my life; I am not naive and not a novice. Nevertheless, nostr is still very much the wild, wild west! There is a DESPERATE need for better documentation, especially documenting the fundamental "how-tos" of getting things like bunkers set up, securing keys, and coordinating things.

Along with that, any nostr tools that can be devised to facilitate these basic operations, including holding users hands through all the setup and establishing of the basics are needed.

I am a (relative) nobody, but even so, in the course of my lifetime, I've established relationships with a few "influencers" whose presence and activity here on nostr might seriously help grow the user base. However, they have been resistant to even trying (in some cases) and (in other cases) have not been active due to the discouragement with how difficult things still are for "the average man."

Please don't get me wrong; I have tremendous admiration and appreciation for all the hard work the devs have done and are continuing to do; but (as I perceive the problem) by and large, the devs are "just TOO CLOSE to things" and (because they already completely understand and know how things work) they have HUGE blind spots when it comes to onboarding normies.

And so, to all my GREATLY APPRECIATED devs: PLEASE take one more hard look at your apps, and especially at EMBEDDED documentation... all the user prompts, all the details and steps of getting "the man in the street" to reach the point where he/she is actually "up and running" with:

* Keypair

* ALL the important PROFILE fields

* A Lightning (or Cashu? or Nuts?) wallet for ZAPPING both in and out

* An appropriate BUNKER for their nsec

* Adequate hand-holding to pull them through ALL of the above

* A VISION for how this will lead to them NEVER AGAIN having to divulge their email address, personal information, etc.

I may have missed something important? Please feel free to expand in comments below.

If YOU have READ THIS FAR; Thank you for listening; please pass this along to your favorite dev(s) in case I've missed someone; and very seriously, THANK YOU, all you cool devs for all your hard work, and please don't take this as a criticism... YOU ARE APPRECIATED!

nostr:nprofile1qyfhwumn8ghj7mmxve3ksctfdch8qatz9uqsuamnwvaz7tmwdaejumr0dshszxthwden5te0dphkgmrzdajzumn0wd68yvfwvdhk6tcqyztuwzjyxe4x2dwpgken87tna2rdlhpd02va5cvvgrrywpddnr3jyhdw0my nostr:nprofile1qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qythwumn8ghj76twvfhhstnwdaehgu3wwa5kuef0qy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz7qpqgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqjt2msn nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7qgwwaehxw309ahx7uewd3hkctcqyqewrqnkx4zsaweutf739s0cu7et29zrntqs5elw70vlm8zudr3y2tpctmc nostr:nprofile1qyghwumn8ghj7vf5xqhxvdm69e5k7tcppemhxue69uhkummn9ekx7mp0qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qpql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afq42ec4h nostr:nprofile1qqs9hejyd252x8q3kw6980ud4lymx3hlx2x3lgg6p7sz58nyv8m2nvgdswkeh nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpq8ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjq2mu9x2

npub1cmmswlckn82se7f2jeftl6ll4szlc6zzh8hrjyyfm9vm3t2afr7svqlr6f

npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm

npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft

nostr:nevent1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tm99ehx7uewd3hkctcpzpmhxue69uhkummnw3ezumt0d5hsz9thwden5te0wfjkccte9ehx7um5wghxyee0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzdmhxue69uhk7enxvd5xz6tw9ec82c30qydhwumn8ghj7un9d3shjtnwdaehgunfvd5x2uewdaexwtcprpmhxue69uhkummnw3ezuendwsh8w6t69e3xj730qqs27uquzt269aqkg8j6qsvt03ascg2uqxammu9q64qycezdjp8k62cm3ppm7

#grownostr

Reply to this note

Please Login to reply.

Discussion

It will all come in time

nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl keeps beating the war-drum about proper documentation.

Yeah. Try setting up a relay. ๐Ÿ™ˆ

The rust one didn't work because of a known, obscure cargo bug, and the strfry runs, but I can't figure out how to see it or interact with it, so that's a bit underwhelming.

Of course, everyone probably thinks I'm too dumb to set up a relay, but whatever.

No.

๐Ÿ˜Ž

Relay devs tend to not get a lot of sats to keep things running and develop nice UIs. :(

Relay operators are doing better. But the dev stuff...

I don't really mind that, and maybe that's something else I could build, but I found four different set of instructions and they all seem to assume that I'm generally familiar with how to interact with relays and just need to know how to set one up.

But I set it up and added an A entry to my DNS (took me a while to figure out what that even meant and then I didn't realize how long it could take to see a result, so I thought I'd done it wrong) and now I'm just staring at the PID and wondering what to do next.

Also found it really weird that the instructions suggest I join a Telegram group for help. I need to join a Telegram group to set up a Nostr relay?

I don't think that. Just the opposite..โค๏ธ๐Ÿซ‚

I tried 3 different relay implementations, ran into inscrutable errors, gave up, and now I just use nostr1.com ๐Ÿ˜…

I use nostr1.com, but we want one to program and test on.

> by and large, the devs are "just TOO CLOSE to things"

Nostr needs (another?) SMALL team of content creators (not devs, particularly) dedicated to documenting the (ever evolving) onboard best practices.

Funding can be found for a dedicated few. I am willing โ€ฆ who joins me? ๐Ÿ‘‹๐Ÿผ

Yes, that's not a bad idea.

Onboarding โ€œbest practiceโ€ documentation is actually a solid part of my current โ€œsocial onboardingโ€ project โ€ฆ (helping friends to share nostr with friends) so this could fold into that nicely.

I imagine the best approach will be to let the โ€œnostr advocatesโ€ write this documentation for themselves.

We might be able to set a nostr wiki site for the purpose โ€ฆ nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft might share his starter code?

nostr:note1xwtq4dg6rvmlxeuv52dt8002dwtfe4gmzkqc96er7v5n7pqv30uqjjecxq

Thanks, Uncle Bob.๐Ÿ™๐Ÿป๐Ÿ˜„๐Ÿ’œ๐Ÿ’–๐Ÿซ‚๐Ÿ˜†๐Ÿ‘

You're listeningโ“

Awesome!๐Ÿ™๐Ÿป๐Ÿซ‚๐Ÿ˜„๐Ÿ’–

I'm repeating myself; and I'd love to hear and--better yet--be helped to understand what it might take for devs to address the concerns I expressed in the note below:

nostr:nevent1qqspge8ks9jlsxpucep2k0eku7x0vvpggjt43v82gxac2zdty3w69lqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzpsvrr7lzv5lhv9jyy82hmdkwuw9cemuvuem3h3juztu9g00ykwdlqvzqqqqqqynlzkhh

I'm happy to interact with any devs willing to try addressing these (perceived) issues. ๐Ÿ˜†๐Ÿ’ฏ