PABLOF7z on Nostr: not just that; it would prevent an app from overwriting a new version of the event it ...
not just that; it would prevent an app from overwriting a new version of the event it hasn't seen
I should have pointed that out explicitly 😅: relays SHOULD reject a replaceable event if the passed in timestamp is not the most recent one
e.g.
### creates event at T+0 seconds
"created_at": 1683015000,
"tags": [ ["d", "replace-me" ] ]
### client 1 replaces event at T+10 seconds
"created_at": 1683015010,
"tags": [ ["d", "replace-me" ], "1683015000" ]
### client 2 fails to replace event at T+20 seconds
"created_at": 1683015020,
"tags": [ ["d", "replace-me" ], "1683015000" ]
I should have pointed that out explicitly 😅: relays SHOULD reject a replaceable event if the passed in timestamp is not the most recent one
e.g.
### creates event at T+0 seconds
"created_at": 1683015000,
"tags": [ ["d", "replace-me" ] ]
### client 1 replaces event at T+10 seconds
"created_at": 1683015010,
"tags": [ ["d", "replace-me" ], "1683015000" ]
### client 2 fails to replace event at T+20 seconds
"created_at": 1683015020,
"tags": [ ["d", "replace-me" ], "1683015000" ]