Ahh, No 3 makes sense. Would be good for businesses addresses I guess.
For No 1, how does work ? I see this address on iris, but on primal and coracle its the npub. Is it client interchangeable ?
For No 2, what does it mean by troubles of key rotation. What is key rotation ?
Btw, can't seem to zap you nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk. I think it been like that for some time
Offf, I am doing some experiments with a personal domain, in fact, lately my incoming zaps have dropped haha.
Can I ask you which client/wallet are you using?
No 1 is related to the ability of the client to search an user by nip-05. Because there is not a standard way to query a relay for a nip-05, the client have to to cache them or use an external service.
An user can have multiple valid addresses, but every client should show only the most recent one, querying the metadata (kind:0) event.
About the key rotation: because a nip-05 is a proxy to the pubkey, if you need to trash the old key and spinup a new one, you don't have to update it everywhere. Users that find your nip-05 (e.g. business card) will find always your update account. Users that already follow you will see an invalid nip-05, and they would be alerted.
On both Amethyst and Coracle I can see your pamela@iris.to address:
Maybe a sync issue? I would be not surprised if clients updates with a different frequency/logic the contact list and the user profile.
