So you would say it’s a Damus issue and not a Nostr issue?
Discussion
What is happening under the hood is a private key/nsec is successfully generated *without* a contact list, a relay list.
Damus accepts the nsec, and does not overwrite the contact list. The rationale is that in certain situations the user might accidentally lose a larger contact list.
This is a crap experience for first time nostr joiners. Will investigate how to improve.
Oh wow. I’m not 100% sure I understand all of the ins and outs of the Nostr protocol, but I think I understand what you’re saying. Thank you for the help. I’ll be sure to recommend a client app directly when pointing someone to Nostr.
This really needs to get prioritized IMO, it’s probably leading to a lot of abandoned npubs and contributing to the “Nostr doesn’t work” myth.
nostr:npub1r9rek7zzenudd0fszwl4q37hr29uvhzf7zefrzddztarx5mx9pzs0faeyf thank you for your patience and persistence. I’ve documented the issue in detail, and am challenging the devs to improve the onboarding experience.