<oembed><type>rich</type><version>1.0</version><title>pjv wrote</title><author_name>pjv (npub1pj…e0h42)</author_name><author_url>https://nostr.now/npub1pjvcwasj9ydasx9nmkf09pftsg640vm5fs7tzprssew8544yj2ds6e0h42</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>If petnames are part of the kind 3 data that clients store publicly on relays then encrypting them would be critical to avoid inadvertent doxxing.&#xA;&#xA;Let&#39;s say I have a friend who has a pubkey they share with me that they want to use anonymously. I follow that pubkey and give it a petname. Then I intentionally (with some clients) or unintentionally (with other clients) save my kind 3 follow list to my write relays.&#xA;&#xA;For that matter, maybe it would be better by default to use kind 30000 (from NIP 51) for saving contact lists to relays for client interoperability and then let kind 3&#39;s only be for intentionally saving public lists of people for other purposes.</html></oembed>