nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 40.md

Browse Source
This commit is contained in:
Thomas 2022-12-14 23:52:12 +01:00
parent b859ae589b
commit 8d3f5c6e79
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
40.md
View File

@ -6,8 +6,7 @@ Expiration Timestamp
`draft` `optional` `author:0xtlt` `draft` `optional` `author:0xtlt`
The `expiration` tag enables users to specify a timestamp at UTC-0 at which the message should be considered expired and deleted by relays (or just ignored by clients). This can be useful for making temporary announcements, making limited-time offers, or sending ephemeral messages but should not be seen as a security solution for the content of your messages. The `expiration` tag enables users to specify a unix timestamp at which the message SHOULD be considered expired (by relays and clients) and SHOULD be deleted by relays.
So be careful when sharing confidential information.
#### Spec #### Spec
@ -39,7 +38,7 @@ Client Behavior
Clients SHOULD use the `supported_nips` field to learn if a relay supports this NIP. Clients SHOULD NOT send expiration events to relays that do not support this NIP. Clients SHOULD use the `supported_nips` field to learn if a relay supports this NIP. Clients SHOULD NOT send expiration events to relays that do not support this NIP.
Clients MUST ignore events that have expired. Clients SHOULD ignore events that have expired.
Relay Behavior Relay Behavior
-------------- --------------