mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-07-28 16:08:29 -04:00
spelling nit
This commit is contained in:
2
22.md
2
22.md
@@ -22,7 +22,7 @@ The motivation for this NIP is to formalize a way for relays to restrict event t
|
|||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
Python Example
|
Python Example
|
||||||
--------------
|
--------------
|
||||||
|
Reference in New Issue
Block a user