forked from nostr-protocol/nips
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
5 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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": <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. | ||
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. |