upleb.uk

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

summaryrefslogtreecommitdiff
path: root/23.md
diff options
context:
space:
mode:
authorfiatjaf <fiatjaf@gmail.com>2023-02-05 20:23:59 -0300
committerfiatjaf <fiatjaf@gmail.com>2023-02-05 20:23:59 -0300
commit16b50a481fa7c373ba8dfbdc92c3b880fecd235a (patch)
treef81439f6744d14771a504c8a5a09fb979164ef6c /23.md
parent0acfd0e84badd3bc54f680e3617ab045a844919c (diff)
rename `nref` to `nitem` and use the `i` tag.
Diffstat (limited to '23.md')
-rw-r--r--23.md15
1 files changed, 7 insertions, 8 deletions
diff --git a/23.md b/23.md
index 1559788..d1353af 100644
--- a/23.md
+++ b/23.md
@@ -24,13 +24,13 @@ These articles are meant to be editable, so they should make use of the replacea
24 24
25### Linking 25### Linking
26 26
27The article may be linked to using the NIP-19 `nref` code along with the `"f"` tag (see NIP-33 and NIP-19). 27The article may be linked to using the NIP-19 `nitem` code along with the `"i"` tag (see NIP-33 and NIP-19).
28 28
29### References 29### References
30 30
31Writing clients should implement support for parsing pasted NIP-19 `nref` identifiers and adding them automatically to the list of `.tags` of the event, replacing the actual content with a string like `#[tag_index]` in the same way as NIP-08 -- or, if the reference is in the form of a URL (for example, `[click here](nref1...)`) then they should be replaced with just the tag number directly as if link with that name existed at the bottom of the Markdown (for example, `[click here][0]`). 31Writing clients should implement support for parsing pasted NIP-19 `nitem` identifiers and adding them automatically to the list of `.tags` of the event, replacing the actual content with a string like `#[tag_index]` in the same way as NIP-08 -- or, if the reference is in the form of a URL (for example, `[click here](nitem1...)`) then they should be replaced with just the tag number directly as if link with that name existed at the bottom of the Markdown (for example, `[click here][0]`).
32 32
33Reader clients should parse the Markdown and replace these references with either internal links so the referenced events can be accessed directly, with NIP-21 `nostr:nref1...` links or direct links to web clients that will handle these references. 33Reader clients should parse the Markdown and replace these references with either internal links so the referenced events can be accessed directly, with NIP-21 `nostr:nitem1...` links or direct links to web clients that will handle these references.
34 34
35The idea here is that having these tags is that reader clients can display a list of backreferences at the bottom when one article mentions another. 35The idea here is that having these tags is that reader clients can display a list of backreferences at the bottom when one article mentions another.
36 36
@@ -44,9 +44,9 @@ Article text:
44title: Lorem Ipsum 44title: Lorem Ipsum
45--- 45---
46 46
47Lorem [ipsum][4] dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. 47Lorem [ipsum][3] dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
48 48
49Read more at #[3]. 49Read more at #[2].
50``` 50```
51 51
52Derived event: 52Derived event:
@@ -58,10 +58,9 @@ Derived event:
58 "title": "Lorem Ipsum\\n---\\n\\nLorem [ipsum][4] dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.\n\nRead more at #[3].", 58 "title": "Lorem Ipsum\\n---\\n\\nLorem [ipsum][4] dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.\n\nRead more at #[3].",
59 "tags": [ 59 "tags": [
60 ["d", "lorem-ipsum"], 60 ["d", "lorem-ipsum"],
61 ["t", "lorem"], 61 ["t", "plceholder"],
62 ["t", "ipsum"],
63 ["e", "b3e392b11f5d4f28321cedd09303a748acfd0487aea5a7450b3481c60b6e4f87", "wss://relay.example.com"], 62 ["e", "b3e392b11f5d4f28321cedd09303a748acfd0487aea5a7450b3481c60b6e4f87", "wss://relay.example.com"],
64 ["f", "a695f6b60119d9521934a691347d9f78e8770b56da16bb255ee286ddf9fda919:ipsum", "wss://relay.nostr.org"] 63 ["i", "30023:a695f6b60119d9521934a691347d9f78e8770b56da16bb255ee286ddf9fda919:ipsum", "wss://relay.nostr.org"]
65 ], 64 ],
66 "pubkey": "...", 65 "pubkey": "...",
67 "id": "..." 66 "id": "..."