upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/23.md
diff options
context:
space:
mode:
authorfiatjaf <fiatjaf@gmail.com>2022-08-14 12:27:27 -0300
committerGitHub <noreply@github.com>2022-08-14 12:27:27 -0300
commitbe92d650b361851880999c812621c658cc01931c (patch)
tree125e2f6d5c0aaee170eb44080b09409274cce2d0 /23.md
parentda3ae71589d237628c02a12920bd4370476560c1 (diff)
improve text
Co-authored-by: Ricardo Arturo Cabral Mejía <me@ricardocabral.io>
Diffstat (limited to '23.md')
-rw-r--r--23.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/23.md b/23.md
index 1ffe5e1..3981376 100644
--- a/23.md
+++ b/23.md
@@ -12,7 +12,7 @@ The content is not used.
12 12
13The tags consist of arrays of 3 elements: the first is the relay URL, the second is the _read_ condition, the third is the _write_ condition. 13The tags consist of arrays of 3 elements: the first is the relay URL, the second is the _read_ condition, the third is the _write_ condition.
14 14
15The _read_ condition consists of a string containing a rule that follows a subset of the [runes](https://pypi.org/project/runes/) language. Specifically only the `|`, `&`, `!`, `>`, `<`, `/` and `=` operators are allowed. When the rule is an empty string it evaluates to `true`. When it consists of a single naked `"!"` it evaluates to `false`. All the operatores must be tested against all possible values in the case of filter values that consist of lists of values and also in the case of event tags that can have multiple values for the same tag -- in other words, the `=` may be interpreted as a `values.any(v => v == runeValue)` instead of an `values == runeValue` operator; the `<` may be interpreted as a `values.any(v => v < runeValue)` and so on. Event tags are identified just by their tag key (for example, `e` or `p`) without the `#` prefix used in filters. 15The _read_ condition consists of a string containing a rule that follows a subset of the [runes](https://pypi.org/project/runes/) language. Specifically only the `|`, `&`, `!`, `>`, `<`, `/` and `=` operators are allowed. When the rule is an empty string it evaluates to `true`. When it consists of a single naked `"!"` it evaluates to `false`. All the operators must be tested against all possible values in the case of filter values that consist of lists of values and also in the case of event tags that can have multiple values for the same tag -- in other words, the `=` may be interpreted as a `values.any(v => v == runeValue)` instead of an `values == runeValue` operator; the `<` may be interpreted as a `values.any(v => v < runeValue)` and so on. Event tags are identified just by their tag key (for example, `e` or `p`) without the `#` prefix used in filters.
16 16
17The `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. 17The `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.
18 18