From 40ec76bb2124adbbc92a73940097c94ed237bbcb Mon Sep 17 00:00:00 2001 From: gudnuf Date: Thu, 17 Oct 2024 12:45:00 -0700 Subject: [PATCH] remove NIP-04 --- 18.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/18.md b/18.md index a6d7491..d16cdec 100644 --- a/18.md +++ b/18.md @@ -67,11 +67,11 @@ Tags are an optional array of `[tag, value, value, ...]` tuples that can be used - type: `nostr` - target: `` -- tags: `[["n","04", "17"]]` +- tags: `[["n", "17"]]` -The `n` tag specifies the NIPs the receiver supports. At lease one type of Nostr direct message MUST be specified. For [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) and [NIP-17](https://github.com/nostr-protocol/nips/blob/master/17.md) direct messages, the sender sends a `PaymentRequestPayload` as the message content. +The `n` tag specifies the NIPs the receiver supports. At least one tag value MUST be specified. For [NIP-17](https://github.com/nostr-protocol/nips/blob/master/17.md) direct messages, the sender sends a `PaymentRequestPayload` as the message content. -Note that the use of NIP-04 direct messages is strongly discouraged, since it reveals metadata about sender and receiver public keys. +[NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) SHOULDNT be used because it is deprecated and reveals metadata about sender and receiver public keys. #### HTTP POST