diff options
| author | vivganes <vivek@vivekganesan.com> | 2023-04-07 17:38:03 +0530 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-04-07 11:45:06 -0300 |
| commit | 3cec80d99ebbee6b72aae31f1856181d04971244 (patch) | |
| tree | 9cbcfcc020dd370a17f5c96aa163736026a68266 /22.md | |
| parent | e219ec64701d89e6b2c3f3ca8fd426d0aefdcb9c (diff) | |
fix grammar and typos
Diffstat (limited to '22.md')
| -rw-r--r-- | 22.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -22,7 +22,7 @@ This NIP formalizes restrictions on event timestamps as accepted by a relay and | |||
| 22 | 22 | ||
| 23 | The event `created_at` field is just a unix timestamp and can be set to a time in the past or future. Relays accept and share events dated to 20 years ago or 50,000 years in the future. This NIP aims to define a way for relays that do not want to store events with *any* timestamp to set their own restrictions. | 23 | The event `created_at` field is just a unix timestamp and can be set to a time in the past or future. Relays accept and share events dated to 20 years ago or 50,000 years in the future. This NIP aims to define a way for relays that do not want to store events with *any* timestamp to set their own restrictions. |
| 24 | 24 | ||
| 25 | [Replaceable events](16.md#replaceable-events) can behave rather unexpected if the user wrote them - or tried to write them - with a wrong system clock. Persisting an update with a backdated system now would result in the update not getting persisted without a notification and if they did the last update with a forward dated system, they will again fail to do another update with the now correct time. | 25 | [Replaceable events](16.md#replaceable-events) can behave rather unexpectedly if the user wrote them - or tried to write them - with a wrong system clock. Persisting an update with a backdated system now would result in the update not getting persisted without a notification and if they did the last update with a forward dated system, they will again fail to do another update with the now correct time. |
| 26 | 26 | ||
| 27 | A wide adoption of this NIP could create a better user experience as it would decrease the amount of events that appear wildly out of order or even from impossible dates in the distant past or future. | 27 | A wide adoption of this NIP could create a better user experience as it would decrease the amount of events that appear wildly out of order or even from impossible dates in the distant past or future. |
| 28 | 28 | ||