diff options
| author | Doug Hoyte <doug@hcsw.org> | 2023-05-19 00:54:44 -0400 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-06-04 18:34:17 -0300 |
| commit | fe9ed69dc3aec54ae437ca09a6d61aa2ce175577 (patch) | |
| tree | e4b99f3b84429f8e370d9f8b551b562912900320 /33.md | |
| parent | cabbaadb69ecf28c2a91ced63359e1bd15b14ea9 (diff) | |
Specify replacement behaviour when replaceable events have the same timestamp
- This is so that relays can converge on a deterministic sets of events, no matter the order they were received
- Otherwise, clients or relays that sync their sets of events could continually retransmit events they think are missing on the other side, wasting bandwidth
Diffstat (limited to '33.md')
| -rw-r--r-- | 33.md | 2 |
1 files changed, 2 insertions, 0 deletions
| @@ -18,6 +18,8 @@ replaceable event with the same kind, author and first `d` tag value being recei | |||
| 18 | SHOULD be discarded, effectively replacing what gets returned when querying for | 18 | SHOULD be discarded, effectively replacing what gets returned when querying for |
| 19 | `author:kind:d-tag` tuples. | 19 | `author:kind:d-tag` tuples. |
| 20 | 20 | ||
| 21 | If two events have the same timestamp, the event with the lowest id (first in lexical order) SHOULD be retained, and the other discarded. | ||
| 22 | |||
| 21 | A missing or a `d` tag with no value should be interpreted equivalent to a `d` tag with the | 23 | A missing or a `d` tag with no value should be interpreted equivalent to a `d` tag with the |
| 22 | value as an empty string. Events from the same author with any of the following `tags` | 24 | value as an empty string. Events from the same author with any of the following `tags` |
| 23 | replace each other: | 25 | replace each other: |