rich1.0Repeatedly nuked profile (npub1hy…wtqnx)https://nostr.now/npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnxnjumphttps://nostr.nowNice. Earlier I was thinking along these lines for DMs to deal with the metadata issue without requiring gift-wrapping. -Bob creates a secondary npub, this npub has no profile -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 -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) -Bob's client adds this code to Bob's profile, similar to adding a TXT record for DNS verification -Bob's client sends a "go check" message to Alice -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. The idea being this would all run over a few seconds, and Alice would not have to know anything about it if the verification failed.