Step 1 of 3
A title for the thread
["subject", text] gives a note a headline. Keep it under about 80 characters.
NIP-14
Subject tag in text events
DraftEvents
Adds a subject tag to kind 1 notes so clients can list threads by title, like email subjects.
At a glance
- Status
- In use and still allowed to change.
- Last changed
- Nov 18, 2023
Try it
Edit the form or the JSON: both stay in sync, the badge says whether the result is valid, and tapping any field explains it.
Not signed yet · Demo keys only. These personas' secret keys are public on purpose.
Explain
Select any field in the form or the JSON to see what it does.
How this NIP works
In the course
No course chapter covers this NIP yet. The editor above is the quickest way in.
Related NIPs
Extends
- NIP-10 Text Notes and Threads
Adds a tag to NIP-10 text notes.
See also
- NIP-17 Private Direct Messages
Private chats use the same tag as the room's topic.
Specification
Specification text is quoted in English from the nostr-protocol/nips repository. Our explanations and the interface are translated. Source on GitHub at commit 0046368
Read the spec132 words, quoted from the repository at commit 0046368.
This NIP defines the use of the "subject" tag in text (kind: 1) events. (implemented in more-speech)
["subject": <string>]
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. 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.