nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 08:55:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: update motivation

Browse Source
This commit is contained in:
Vlad Stan 2023-04-10 09:26:38 +03:00 committed by GitHub
parent c55a29ff6c
commit 6e10e94e3c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
704.md
View File

@ -11,6 +11,8 @@ This NIP defines a way for two clients to derive `one-use-only` keys for sending
## Motivation ## Motivation
The content of `Direct Messages` [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) is encrypted, but everyone can see who is chatting with whom. This is far from ideal from a privacy perspective. The content of `Direct Messages` [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) is encrypted, but everyone can see who is chatting with whom. This is far from ideal from a privacy perspective.
This NIP describes a way to obfuscate DM communications from the "general public", it does not deal with the relay tracking of clients (for that see [NIP XXX](xxx)).
## Suggestion ## Suggestion
For the maximum of privacy the two participants of a `Direct Message` exchange SHOULD use a different public key for each `kind:4` event. For the maximum of privacy the two participants of a `Direct Message` exchange SHOULD use a different public key for each `kind:4` event.
This means that each participant has to: This means that each participant has to: