Fair to say then a unique identifier thats usable by multiple nostr apps not just Primal?
If you're sharing the npub already that's ideal, but only works where copy/paste is available... I think you mean a search term that users can use in whatever app they're already into? (as opposed to a URL)
can't just choose a username
Bingo, I see this too.
I think this is at the crux of the username problem, there's no consistent application of them across the Nostr apps because every search would have to respond with strictly an opinion on who dk should belong to.
My ruminations on this are as follows, we should only need a very loose framework for arriving at those opinions. It can't get anymore fractured than it already is.
By self declaring dk, having followers that label you as dk, perhaps some other metrics from their relay that add to a rank, Primal could easily give you weight over a lesser and rogue claimant of dk.
Reputational conflict resolution.
This is non-authoritative and not truly unique ofc. It gets interesting when another platform sells influence, and takes money to assign the name dk to someone else in their social graph that users may bootstrap from. Since their social graph differs, users weighting that platform resolve a different dk. This is basically what we have today.
Which begs the next question,
Is the incentive stronger to sell reputation, or is consistency with social consensus rewarded more?
My theory is the latter, going against social conensus will eventually render what you're selling worthless. If correct, its relatively simple from a technical standpoint because it's still mostly open to interpretation (worst protocol theory) how to weight a social graph.
dk
should belong to.dk
, having followers that label you asdk
, perhaps some other metrics from their relay that add to a rank, Primal could easily give you weight over a lesser and rogue claimant ofdk
.dk
to someone else in their social graph that users may bootstrap from. Since their social graph differs, users weighting that platform resolve a differentdk
. This is basically what we have today.