Trying to go with compression on

This commit is contained in:
Vitor Pamplona 2024-02-23 19:10:58 -05:00
parent c8f03b6de4
commit 713bea60c2

4
19.md
View File

@ -36,7 +36,7 @@ These are the possible bech32 prefixes with `TLV`:
- `nevent`: a nostr event id - `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 - `nembed`: a compressed nostr event
These possible standardized `TLV` types are indicated here: 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 `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 - for `nembed`, it is a JSON-stringified, GZIP-compressed 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