rename coordinates: nitem->naddr, "i"->"a"

This commit is contained in:
fiatjaf
2023-02-13 08:47:23 -03:00
parent a85067ec68
commit b4493aa56a
4 changed files with 12 additions and 11 deletions

10
19.md
View File

@@ -35,7 +35,7 @@ These are the possible bech32 prefixes with `TLV`:
- `nprofile`: a nostr profile
- `nevent`: a nostr event
- `nrelay`: a nostr relay
- `nitem`: a nostr parameterized replaceable event coordinate (NIP-33)
- `naddr`: a nostr parameterized replaceable event coordinate (NIP-33)
These possible standardized `TLV` types are indicated here:
@@ -44,14 +44,14 @@ These possible standardized `TLV` types are indicated here:
- for `nprofile` it will be the 32 bytes of the profile public key
- for `nevent` it will be the 32 bytes of the event id
- for `nrelay`, this is the relay URL
- for `nitem`, it is the identifier (the `"d"` tag) of the event being referenced
- for `naddr`, it is the identifier (the `"d"` tag) of the event being referenced
- `1`: `relay`
- for `nprofile`, `nevent` and `nitem`, a relay in which the entity (profile or event) is more likely to be found, encoded as ascii
- for `nprofile`, `nevent` and `naddr`, a relay in which the entity (profile or event) is more likely to be found, encoded as ascii
- this may be included multiple times
- `2`: `author`
- for `nitem`, the 32 bytes of the pubkey of the event
- for `naddr`, the 32 bytes of the pubkey of the event
- `3`: `kind`
- for `nitem`, the 32-bit unsigned integer of the kind, big-endian
- for `naddr`, the 32-bit unsigned integer of the kind, big-endian
## Examples