From 56cc238a4159c5b52c0b4f0edabcd3a189134dbc Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Sun, 14 Aug 2022 20:22:16 -0300 Subject: [PATCH] text fixes. Co-authored-by: Leo Wandersleb --- 23.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/23.md b/23.md index f750ff9a..f9ef5575 100644 --- a/23.md +++ b/23.md @@ -16,7 +16,9 @@ The _read_ condition consists of a string containing a rule that follows a subse The `read` rule operates on the values of the [NIP-01](01.md) **filter** object, while the `write` rule operates on the values of the **event** object. -When a `read` rule evaluates to `true` for a given **filter** the client SHOULD send a `REQ` message to the relay, otherwise it SHOULD NOT. When a `write` rule evaluates to `true` for a given **event** the client SHOULD send that event (in a `EVENT` message) to the relay, otherwise it MUST NOT. +When a `read` rule evaluates to `false` for a given **filter** the client SHOULD NOT send that filter in a `REQ` message to that relay. + +When a `write` rule evaluates to `false` for a given **event** the client SHOULD NOT send that event in an `EVENT` message to that relay. When a rule is malformed or the client is unable to parse it for any reason (for example, for not having implemented all the operators) it SHOULD treat it as `true` if it is a _read_ rule and `false` if it is a _write_ rule.