diff options
| author | Jeff Thibault <jdthibault2@gmail.com> | 2022-08-13 14:08:14 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-13 14:08:14 -0400 |
| commit | 6ee98c1bfbe5f4c28fd55bdc835b9a5621e5cab9 (patch) | |
| tree | 0e0b56e4c1823531884217433000fdd9b854c8f0 /22.md | |
| parent | f5852fda8334c10bc72402f99ffabe093ce1b899 (diff) | |
spelling nit
Diffstat (limited to '22.md')
| -rw-r--r-- | 22.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -22,7 +22,7 @@ The motivation for this NIP is to formalize a way for relays to restrict event t | |||
| 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. For example, the `created_at` field can be set to a time 20 years ago even though it was created today and still be a valid event. It can also be set to a time 20 years in the future and still be a valid event. 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. For example, the `created_at` field can be set to a time 20 years ago even though it was created today and still be a valid event. It can also be set to a time 20 years in the future and still be a valid event. 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 | A wide adoption of this could create a better UX on clients as well because it would decrease the liklihood of the user seeing events from dates such as 1984 or 2084, which could be confusing. | 25 | A wide adoption of this could create a better UX on clients as well because it would decrease the likelihood of the user seeing events from dates such as 1984 or 2084, which could be confusing. |
| 26 | 26 | ||
| 27 | Python Example | 27 | Python Example |
| 28 | -------------- | 28 | -------------- |