diff options
| author | shafemtol <sha@femtol.net> | 2023-03-05 20:49:57 +0000 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-03-05 22:26:09 -0300 |
| commit | b8e657bb3764af8bec952a6e3d5d8d3319abccf9 (patch) | |
| tree | 759cd7c5d89db18686e0b7da07482c87346fdcac | |
| parent | d97928bd9024a988be6c9f7ec18c0fcf93a8b9a3 (diff) | |
NIP-08: Specify nonmatch behavior
| -rw-r--r-- | 08.md | 2 |
1 files changed, 2 insertions, 0 deletions
| @@ -15,3 +15,5 @@ Once a mention is identified, for example, the pubkey `27866e9d854c78ae625b867ee | |||
| 15 | The same process applies for mentioning event IDs. | 15 | The same process applies for mentioning event IDs. |
| 16 | 16 | ||
| 17 | A client that receives a `text_note` event with such `#[index]` mentions in its `.content` CAN do a search-and-replace using the actual contents from the `.tags` array with the actual pubkey or event ID that is mentioned, doing any desired context augmentation (for example, linking to the pubkey or showing a preview of the mentioned event contents) it wants in the process. | 17 | A client that receives a `text_note` event with such `#[index]` mentions in its `.content` CAN do a search-and-replace using the actual contents from the `.tags` array with the actual pubkey or event ID that is mentioned, doing any desired context augmentation (for example, linking to the pubkey or showing a preview of the mentioned event contents) it wants in the process. |
| 18 | |||
| 19 | Where `#[index]` has an `index` that is outside the range of the tags array or points to a tag that is not an `e` or `p` tag or a tag otherwise declared to support this notation, the client MUST NOT perform such replacement or augmentation, but instead display it as normal text. | ||