diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-02-05 20:23:59 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-02-05 20:23:59 -0300 |
| commit | 16b50a481fa7c373ba8dfbdc92c3b880fecd235a (patch) | |
| tree | f81439f6744d14771a504c8a5a09fb979164ef6c /33.md | |
| parent | 0acfd0e84badd3bc54f680e3617ab045a844919c (diff) | |
rename `nref` to `nitem` and use the `i` tag.
Diffstat (limited to '33.md')
| -rw-r--r-- | 33.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -38,11 +38,11 @@ Normally (as per NIP-01, NIP-12) the `"p"` tag is used for referencing public ke | |||
| 38 | equivalents for event tags (i.e. an `nprofile` is generally translated into a tag | 38 | equivalents for event tags (i.e. an `nprofile` is generally translated into a tag |
| 39 | `["p", "<event hex id>", "<relay url>"]`). | 39 | `["p", "<event hex id>", "<relay url>"]`). |
| 40 | 40 | ||
| 41 | To support linking to parameterized replaceable events, the `nref` code is introduced on | 41 | To support linking to parameterized replaceable events, the `nitem` code is introduced on |
| 42 | NIP-19. It includes the public key of the event author and the `d` tag (and relays) such that | 42 | NIP-19. It includes the public key of the event author and the `d` tag (and relays) such that |
| 43 | the referenced combination of public key and `d` tag can be found. | 43 | the referenced combination of public key and `d` tag can be found. |
| 44 | 44 | ||
| 45 | The equivalent in `tags` to the `nref` code is the tag `"f"`, comprised of `["f", "<pubkey>:<d-identifier>", "<relay url>"]`. | 45 | The equivalent in `tags` to the `nitem` code is the tag `"i"`, comprised of `["i", "<kind>:<pubkey>:<d-identifier>", "<relay url>"]`. |
| 46 | 46 | ||
| 47 | Client Behavior | 47 | Client Behavior |
| 48 | --------------- | 48 | --------------- |