{"type":"rich","version":"1.0","title":"Repeatedly nuked profile wrote","author_name":"Repeatedly nuked profile (npub1hy…wtqnx)","author_url":"https://nostr.now/npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnx","provider_name":"njump","provider_url":"https://nostr.now","html":"Nice. Earlier I was thinking along these lines for DMs to deal with the metadata issue without requiring gift-wrapping. \n\n-Bob creates a secondary npub, this npub has no profile\n-Bob messages Alice from the secondary npub with a special event called an 'It's me message' (IMM) or some such thing. This templated message contains Bob's actual npub \n-Alice's client receives the IMM and sends back an IMM return (also an event type, contains a code valid for a period of time) \n-Bob's client adds this code to Bob's profile, similar to adding a TXT record for DNS verification \n-Bob's client sends a \"go check\" message to Alice\n-Alice's client sees the code on Bob's profile and marks the DM chat as as being with Bob. Code is no longer needed.\n\nThe idea being this would all run over a few seconds, and Alice would not have to know anything about it if the verification failed."}