From ebacbccda8c27ce259e3288af0f51026904ba5a7 Mon Sep 17 00:00:00 2001 From: "Robert C. Martin" Date: Tue, 24 May 2022 07:33:11 -0500 Subject: [PATCH] Nip-14 for subject tag --- Proposal-Subject-Discussion.md => 14.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) rename Proposal-Subject-Discussion.md => 14.md (65%) diff --git a/Proposal-Subject-Discussion.md b/14.md similarity index 65% rename from Proposal-Subject-Discussion.md rename to 14.md index cf9ee19a..0b37e8aa 100644 --- a/Proposal-Subject-Discussion.md +++ b/14.md @@ -1,22 +1,19 @@ -NIP-?? +NIP-14 ====== -I am implementing this as a trial in more-speech. - Subject tag in Text events. --------------------------- `draft` `optional` `author:unclebobmartin` -This NIP defines the use of the Subject tag in text (kind: 1) events. - -Subject -------- +This NIP defines the use of the "subject" tag in text (kind: 1) events. +(implemented in more-speech) `["subject": ]` Browsers often display threaded lists of messages. The contents of the subject tag can be used in such lists, instead of the more ad hoc approach of using the first few words of the message. This is very similar to the way email browsers display lists of incoming emails by subject rather than by contents. -When replying to a message with a subject, clients should replicate the subject tag. +When replying to a message with a subject, clients SHOULD replicate the subject tag. Clients MAY adorn the subject to denote +that it is a reply. e.g. by prepending "Re:". Subjects should generally be shorter than 80 chars. Long subjects will likely be trimmed by clients.