From 713bea60c2f609610dae074345388848bb3fecbb Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Fri, 23 Feb 2024 19:10:58 -0500 Subject: [PATCH] Trying to go with compression on --- 19.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/19.md b/19.md index 29a55564..4d48ec3f 100644 --- a/19.md +++ b/19.md @@ -36,7 +36,7 @@ These are the possible bech32 prefixes with `TLV`: - `nevent`: a nostr event id - `nrelay`: a nostr relay - `naddr`: a nostr _replaceable event_ coordinate - - `nembed`: a stringified nostr event + - `nembed`: a compressed nostr event These possible standardized `TLV` types are indicated here: @@ -46,7 +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 + - for `nembed`, it is a JSON-stringified, GZIP-compressed 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