From ee4011d84e82086a10101f496b8c285c3a330d8d Mon Sep 17 00:00:00 2001 From: arthurfranca Date: Fri, 9 Feb 2024 19:22:48 -0300 Subject: [PATCH] Add event requesting instructions --- 00.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/00.md b/00.md index a4892f1..cf0f851 100644 --- a/00.md +++ b/00.md @@ -41,7 +41,7 @@ It uses the custom NIP-42 event serialization for events that require `AUTH`. The `.content` and other tags aren't fixed. The structure depends on the kind of the public event it is protecting. For example, if it is -protecting a `kind:30023`, it should have the structure defined on [NIP-23](23.md). +protecting a `kind:30023` event, it should have the structure defined on [NIP-23](23.md). Example: @@ -61,3 +61,17 @@ Example: ... } ``` + +## Requesting the Event + +The client is expected to initially request the public event. For example, a microblogging client +will request `kind:1` events as usual. + +If one of these events includes a `full_event` tag, +the client should request it with a filter that includes +a `#A` filter key set to the client's user pubkey. + +If the user has rights to access the full event, the relay will send it +after the NIP-42 authentication flow. + +For example: `{ kinds: [30042], authors: ["abc"], #d: ["xyz"], #A: [""], limit: 1 }`