From 8d3f5c6e79cc25a59e8148b6a98c1cac8f960159 Mon Sep 17 00:00:00 2001 From: Thomas <31560900+0xtlt@users.noreply.github.com> Date: Wed, 14 Dec 2022 23:52:12 +0100 Subject: [PATCH] Update 40.md --- 40.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/40.md b/40.md index 8aa9538..d99aef5 100644 --- a/40.md +++ b/40.md @@ -6,8 +6,7 @@ Expiration Timestamp `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. -So be careful when sharing confidential information. +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. #### 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 MUST ignore events that have expired. +Clients SHOULD ignore events that have expired. Relay Behavior --------------