Right, but it becomes harder to query those events, since you don't know who might be contacting you. ArcadeCity did something like this, but it only works for expected DMs (which could be considered a feature). The new gift wrap approach uses wrapping with ephemeral keys to prevent correlation while keeping addressing intact. So it's known that someone received a message, but not who sent it. Timing and padding attacks are also mitigated by timestamp randomization within a range and padding in the ciphertext. Relay fingerprinting is harder to avoid, but if you use a trusted relay or a proxy that can be mitigated as well.
Discussion
Is there a NIP for this? I don't see anything for "giftwrap" in the nips repo, nor anything interesting for "DM" or "direct" outside of NIP-04
Trusted relays is a hard pill to swallow, but it's still vastly better for your relay to have metadata than for *everybody* to.
Yep, https://github.com/nostr-protocol/nips/issues/717 is the main thread, you can follow the links to draft NIP 44 and NIP 24 for more detail
Ah thanks, didn't check issues and PRs, just my local copy of the nips repo. Can't wait for issues+PRs on nostr already...
solving this problem is something that Indra would do. i was gonna build it but i have to get something paying sooner and my buddy who was paying me to build the protocol seems keen on taking over the task at some point, but not sure when he's gonna actually start.
indra would also provide a solution to private/anonymous relay service.
(paid that is)
Hadn't heard of that before, are you talking about https://github.com/indra-labs/indra ?