fix/improve limbo onboarding (nostr dot com)

[alltheseas]

what happens

flow

1. keys are generated externally to damus iOS (nostr.com)
2. keys are input to damus, and contact list and relay list remain in limbo/not created.

https://github.com/nostrability/nostrability/issues/223

conflict & commentary/suggestion

Damus first aid functionality fixes the above describe issues of limbo contact and/or relay list.

Will advises that overwriting contact list is dangerous and an anti-pattern.

However if above issue is not fixed for the newcomer, onboarding rates will remain handicapped.

[linear[bot]]

IOS-2051 fix limbo onboarding

[alltheseas]

https://damus.io/nevent1qqsyf9nqzhj9sjuqzuxkupx5t95t47qqffyqaxgzk9s0nnr2f4fruvq3qh60q

“I’ve seen this problem occur both with keys created via Damus as well as other clients including Primal. I don’t have too much specific I can offer, only that Damus is one of the more frustrating clients when it comes to seeing newly created profiles, as well as publishing profile edits for new users with the default relay set.”

[alltheseas]

@dmnyc thanks for the feedback - dev team to investigate this crappy onboarding experience

[alltheseas]

If can't find list(s), ask the user. For example,

"Have you used other apps?"

[alltheseas]

Relationship status as a potential solution? Seems bigger problem than damus, and nostr dot com issue

[alltheseas]

https://github.com/nostr-protocol/nips/pull/761