Yup.
A npub on its own is just a npub. That’s why I believe NIP-05 is a good start, though not the eventual solution. Reputation is a function of context: over time, the events that a npub emits, over relationships: the ‘web’ in which the npub is judged to be a good part.
Not sure we have the solution yet, but what is encouraging is that, with #nostr, we have a different starting point than other so-called solutions that have a permissioned starting point.
You have a keyring of identities which change in time. The NIP-05 is tied to a domain. The nostr id is tied to a pubkey. The pubkey could be looked up from a number of relays which give a signed profile. But those profiles can also live on domains in .well-known locatations too, the only difference is that relays reply in realtime. You can version control the profile as it evovles stamp it in time, and also track it on a block chain.
Thanks. Let me digest this.
