upleb.uk

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

summaryrefslogtreecommitdiff
path: root/14.md
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 /14.md
parentee0c337eed5c0e01edf5bf0e838e52284ce05075 (diff)
Nip-14 for subject tag
Diffstat (limited to '14.md')
-rw-r--r--14.md19
1 files changed, 19 insertions, 0 deletions
diff --git a/14.md b/14.md
new file mode 100644
index 0000000..0b37e8a
--- /dev/null
+++ b/14.md
@@ -0,0 +1,19 @@
1NIP-14
2======
3
4Subject tag in Text events.
5---------------------------
6
7`draft` `optional` `author:unclebobmartin`
8
9This NIP defines the use of the "subject" tag in text (kind: 1) events.
10(implemented in more-speech)
11
12`["subject": <string>]`
13
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.
15
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:".
18
19Subjects should generally be shorter than 80 chars. Long subjects will likely be trimmed by clients.