From a1d24586a2ed869df4e9fac94ded39979648ebbf Mon Sep 17 00:00:00 2001 From: Vlad Stan Date: Mon, 10 Apr 2023 16:06:33 +0300 Subject: [PATCH] Update 705.md --- 705.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/705.md b/705.md index 41bfc796..87832cc7 100644 --- a/705.md +++ b/705.md @@ -14,13 +14,14 @@ One way to increase the privacy of Encrypted Direct Messages ([NIP-04](https://g This technique hides from the "general public" that two clients are chatting. However, the relay(s) in the middle can still see who is publishing events and who is listening for events with specific public keys (and correlate the two). ## Suggestion -Any client can ask its peers to re-publish messages on its behalf. The simplified version of the interaction is as follows: +Any client can ask its peers to `re-publish` messages on its behalf. The simplified version of the interaction is as follows: - `Alice` wants to chat with `Bob`. She builds the `kind:4` nostr event but does NOT sent it to the relay(s). - instead `Alice` creates a `kind:4` event for `Carol` where the content is the event for `Bob`. `Alice` publishes this event to the relay(s). -- `Carol` receives the event, unwrapps it and publishes to the relay(s) the event for `Bob`. +- `Carol` receives the event, unwrapps it then publishes to the relay(s) the event for `Bob`. - the relay(s) see the event as coming from `Carol` instead of `Alice` People can easily run very lightweight republish services for free and provide anonymity for everybody else. +Re-publish services can also be an optional component of chat clients. ## Implementation Define a new [NIP-16](https://github.com/nostr-protocol/nips/blob/master/16.md) `republish` event with `kind:20001` (ephemeral) in the form: