upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert C. Martin <unclebob@cleancoder.com>2022-05-24 07:33:11 -0500
committerRobert C. Martin <unclebob@cleancoder.com>2022-05-24 07:33:11 -0500
commitebacbccda8c27ce259e3288af0f51026904ba5a7 (patch)
tree7a3fa04a7bb8ea80a70763ae59d785b56df66888
parentee0c337eed5c0e01edf5bf0e838e52284ce05075 (diff)
Nip-14 for subject tag
-rw-r--r--14.md (renamed from Proposal-Subject-Discussion.md)13
1 files changed, 5 insertions, 8 deletions
diff --git a/Proposal-Subject-Discussion.md b/14.md
index cf9ee19..0b37e8a 100644
--- a/Proposal-Subject-Discussion.md
+++ b/14.md
@@ -1,22 +1,19 @@
1NIP-?? 1NIP-14
2====== 2======
3 3
4I am implementing this as a trial in more-speech.
5
6Subject tag in Text events. 4Subject tag in Text events.
7--------------------------- 5---------------------------
8 6
9`draft` `optional` `author:unclebobmartin` 7`draft` `optional` `author:unclebobmartin`
10 8
11This NIP defines the use of the Subject tag in text (kind: 1) events. 9This NIP defines the use of the "subject" tag in text (kind: 1) events.
12 10(implemented in more-speech)
13Subject
14-------
15 11
16`["subject": <string>]` 12`["subject": <string>]`
17 13
18Browsers 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. 14Browsers 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.
19 15
20When replying to a message with a subject, clients should replicate the subject tag. 16When replying to a message with a subject, clients SHOULD replicate the subject tag. Clients MAY adorn the subject to denote
17that it is a reply. e.g. by prepending "Re:".
21 18
22Subjects should generally be shorter than 80 chars. Long subjects will likely be trimmed by clients. 19Subjects should generally be shorter than 80 chars. Long subjects will likely be trimmed by clients.