mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-12 18:36:24 +00:00
Embedding events into other event's texts.
This commit is contained in:
parent
4313fbf7a5
commit
c8f03b6de4
4
19.md
4
19.md
@ -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`:
|
||||
|
||||
- `nprofile`: a nostr profile
|
||||
- `nevent`: a nostr event
|
||||
- `nevent`: a nostr event id
|
||||
- `nrelay`: a nostr relay
|
||||
- `naddr`: a nostr _replaceable event_ coordinate
|
||||
- `nembed`: a stringified nostr event
|
||||
|
||||
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 `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 `nembed`, it is a JSON-stringified event
|
||||
- `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
|
||||
- this may be included multiple times
|
||||
|
Loading…
Reference in New Issue
Block a user