Embedding events into other event's texts.

This commit is contained in:
Vitor Pamplona 2024-02-23 09:54:12 -05:00
parent 4313fbf7a5
commit c8f03b6de4

4
19.md
View File

@ -33,9 +33,10 @@ For these events, the contents are a binary-encoded list of `TLV` (type-length-v
These are the possible bech32 prefixes with `TLV`: These are the possible bech32 prefixes with `TLV`:
- `nprofile`: a nostr profile - `nprofile`: a nostr profile
- `nevent`: a nostr event - `nevent`: a nostr event id
- `nrelay`: a nostr relay - `nrelay`: a nostr relay
- `naddr`: a nostr _replaceable event_ coordinate - `naddr`: a nostr _replaceable event_ coordinate
- `nembed`: a stringified nostr event
These possible standardized `TLV` types are indicated here: These possible standardized `TLV` types are indicated here:
@ -45,6 +46,7 @@ These possible standardized `TLV` types are indicated here:
- for `nevent` it will be the 32 bytes of the event id - for `nevent` it will be the 32 bytes of the event id
- for `nrelay`, this is the relay URL - for `nrelay`, this is the relay URL
- for `naddr`, it is the identifier (the `"d"` tag) of the event being referenced. For non-parameterized replaceable events, use an empty string. - for `naddr`, it is the identifier (the `"d"` tag) of the event being referenced. For non-parameterized replaceable events, use an empty string.
- for `nembed`, it is a JSON-stringified event
- `1`: `relay` - `1`: `relay`
- for `nprofile`, `nevent` and `naddr`, _optionally_, a relay in which the entity (profile or event) is more likely to be found, encoded as ascii - for `nprofile`, `nevent` and `naddr`, _optionally_, a relay in which the entity (profile or event) is more likely to be found, encoded as ascii
- this may be included multiple times - this may be included multiple times