diff options
| author | Asai Toshiya <to.asai.60@gmail.com> | 2023-07-19 12:34:07 +0900 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-07-21 10:33:05 -0300 |
| commit | b503f8a92b22be3037b8115fe3e644865a4fa155 (patch) | |
| tree | 2cec04c3916e28278e8269ab5f0476d3b134db12 /01.md | |
| parent | fe2009b459c4dfcef158e745847ef01376b1d12a (diff) | |
Clarify sort order when specified limit
Diffstat (limited to '01.md')
| -rw-r--r-- | 01.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -84,7 +84,7 @@ All conditions of a filter that are specified must match for an event for it to | |||
| 84 | 84 | ||
| 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. | 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. |
| 86 | 86 | ||
| 87 | The `limit` property of a filter is only valid for the initial query and can be ignored afterward. When `limit: n` is present it is assumed that the events returned in the initial query will be the latest `n` events. It is safe to return less events than `limit` specifies, but it is expected that relays do not return (much) more events than requested so clients don't get unnecessarily overwhelmed by data. | 87 | The `limit` property of a filter is only valid for the initial query and can be ignored afterward. When `limit: n` is present it is assumed that the events returned in the initial query will be the last `n` events ordered by the `created_at`. It is safe to return less events than `limit` specifies, but it is expected that relays do not return (much) more events than requested so clients don't get unnecessarily overwhelmed by data. |
| 88 | 88 | ||
| 89 | ### From relay to client: sending events and notices | 89 | ### From relay to client: sending events and notices |
| 90 | 90 | ||