From c8f03b6de44e3102741f085847b2b429364bdbd5 Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Fri, 23 Feb 2024 09:54:12 -0500 Subject: [PATCH] Embedding events into other event's texts. --- 19.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/19.md b/19.md index ef808870..29a55564 100644 --- a/19.md +++ b/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