{"id":"5b176263ed00eb208b8552c77d9bc0415321f0dfc5a6a239c6b47ea0bf8a1ee4","pubkey":"2b39b4ffe62933df970e19366c22c1e092f953f83fcfed754e0f04d5a3b459f9","created_at":1700309592,"kind":30817,"tags":[["d","nip-14"],["title","NIP-14: Subject tag in text events"],["summary","The subject tag, which gives a note a heading the way an email has one."],["s","draft"],["t","nostr"],["t","nip"],["alt","A specification: NIP-14: Subject tag in text events"],["client","openspecs-import"],["published_at","1653160669"],["proxy","https://github.com/nostr-protocol/nips/blob/656cecc7c0a815b6a2b218d3b5d6f078b3f4dbab/14.md","web"],["x","537dd4f6dcbabad8fa4080f74cf52b3f5062659aad1887575094d2e7c21042ed"]],"content":"NIP-14\n======\n\nSubject tag in Text events\n--------------------------\n\n`draft` `optional`\n\nThis NIP defines the use of the \"subject\" tag in text (kind: 1) events.\n(implemented in more-speech)\n\n```json\n[\"subject\": <string>]\n```\n\nBrowsers 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.\n\nWhen replying to a message with a subject, clients SHOULD replicate the subject tag.  Clients MAY adorn the subject to denote\nthat it is a reply.  e.g. by prepending \"Re:\".\n\nSubjects should generally be shorter than 80 chars.  Long subjects will likely be trimmed by clients.\n","sig":"24c3d4a0cb536e181f26b1229a586b9b85ae24671b9397869873ec2b1715668363c7c198fdb21e89510e538431b4e7c168db598b28c1996c6f7f17e5420fe03f"}