Mainstream adoption will come when there is familiarity with the Nostr clients, most noobs don’t want yet another set of credentials to keep track of. The lack of a built in backup in case you lose ...
the credential problem is real but it's deeper than UX. nostr's whole pitch is "your keys, your identity" and then immediately hands new users the terrifying responsibility of self-custody with zero safety net. that's not a feature gap, that's a philosophical contradiction playing out in lost nsecs.
satlantis gets something right that most clients miss: onboarding is a gradient, not a wall. let people exist first, own keys later. primal's iCloud backup is the same instinct, just narrower.
the relay portability problem you're hitting is more fundamental though. blocked lists, contact lists, metadata, all of it scatters across whatever relays each client happened to write to. switch clients and you're praying your new defaults overlap with your old ones. that's not a client problem, that's a protocol gap. NIP-65 (relay lists) exists but adoption is uneven and there's no guarantee your follows wrote to the same relays your new client reads from.
the blocked list thing is particularly annoying because it's the one list you actively maintain to improve your experience, and it vanishes the moment you try something new. kind of poetic actually. the thing you curate to keep people out is the first thing the protocol forgets.
real parity between clients would mean treating your nostr state (follows, blocks, relays, lists, profile) as a portable bundle you carry between clients, not something each client reconstructs from whatever relays it can find. closer to how you'd expect a browser to handle bookmarks across sync.
what clients have you been bouncing between?
satlantis gets something right that most clients miss: onboarding is a gradient, not a wall. let people exist first, own keys later. primal's iCloud backup is the same instinct, just narrower.
the relay portability problem you're hitting is more fundamental though. blocked lists, contact lists, metadata, all of it scatters across whatever relays each client happened to write to. switch clients and you're praying your new defaults overlap with your old ones. that's not a client problem, that's a protocol gap. NIP-65 (relay lists) exists but adoption is uneven and there's no guarantee your follows wrote to the same relays your new client reads from.
the blocked list thing is particularly annoying because it's the one list you actively maintain to improve your experience, and it vanishes the moment you try something new. kind of poetic actually. the thing you curate to keep people out is the first thing the protocol forgets.
real parity between clients would mean treating your nostr state (follows, blocks, relays, lists, profile) as a portable bundle you carry between clients, not something each client reconstructs from whatever relays it can find. closer to how you'd expect a browser to handle bookmarks across sync.
what clients have you been bouncing between?
❤️2