diff options
| author | jiftechnify <jiftech.stlfy@gmail.com> | 2023-07-09 17:31:08 +0900 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-07-14 12:45:46 -0300 |
| commit | d1814405beac7a936fa0dedc08359d70b5a9ab48 (patch) | |
| tree | 742b46f06297740d7e4dc6fe372d1bf36ae62cbb | |
| parent | 20b9bb787bc1d4f6a70c34491448afa39f358ff5 (diff) | |
add detailed description of since/until
| -rw-r--r-- | 01.md | 2 |
1 files changed, 2 insertions, 0 deletions
| @@ -78,6 +78,8 @@ Filter attributes containing lists (such as `ids`, `kinds`, or `#e`) are JSON ar | |||
| 78 | 78 | ||
| 79 | The `ids` and `authors` lists contain lowercase hexadecimal strings, which may either be an exact 64-character match, or a prefix of the event value. A prefix match is when the filter string is an exact string prefix of the event value. The use of prefixes allows for more compact filters where a large number of values are queried, and can provide some privacy for clients that may not want to disclose the exact authors or events they are searching for. | 79 | The `ids` and `authors` lists contain lowercase hexadecimal strings, which may either be an exact 64-character match, or a prefix of the event value. A prefix match is when the filter string is an exact string prefix of the event value. The use of prefixes allows for more compact filters where a large number of values are queried, and can provide some privacy for clients that may not want to disclose the exact authors or events they are searching for. |
| 80 | 80 | ||
| 81 | The `since` and `until` properties can be used to specify the time range of events returned in the subscription. If a filter includes the `since` property, events with `created_at` greater than or equal to `since` are considered to match the filter. The `until` property is similar except that `created_at` must be less than or equal to `until`. In short, an event matches a filter if `since <= created_at <= until` holds. | ||
| 82 | |||
| 81 | All conditions of a filter that are specified must match for an event for it to pass the filter, i.e., multiple conditions are interpreted as `&&` conditions. | 83 | All conditions of a filter that are specified must match for an event for it to pass the filter, i.e., multiple conditions are interpreted as `&&` conditions. |
| 82 | 84 | ||
| 83 | A `REQ` message may contain multiple filters. In this case, events that match any of the filters are to be returned, i.e., multiple filters are to be interpreted as `||` conditions. | 85 | A `REQ` message may contain multiple filters. In this case, events that match any of the filters are to be returned, i.e., multiple filters are to be interpreted as `||` conditions. |