diff options
| author | michaelhall923 <michaelhall923@protonmail.com> | 2023-04-21 09:04:20 -0400 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-04-21 10:17:36 -0300 |
| commit | c5f43a8f9047184258f0e59f3e1fcd759acca4e2 (patch) | |
| tree | 7c38ec2a2f907d5ce5e7a535ccfd68d96082f5a6 /01.md | |
| parent | 4b9847802a9fb1a6d13b3967976bca78b5eacb0c (diff) | |
Update 01.md
Info on "e" and "p" tags is kind of hard to find so I added a link to it in the place that I intuitively looked for it.
Diffstat (limited to '01.md')
| -rw-r--r-- | 01.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -107,5 +107,5 @@ A relay may choose to treat different message kinds differently, and it may or m | |||
| 107 | ## Other Notes: | 107 | ## Other Notes: |
| 108 | 108 | ||
| 109 | - Clients should not open more than one websocket to each relay. One channel can support an unlimited number of subscriptions, so clients should do that. | 109 | - Clients should not open more than one websocket to each relay. One channel can support an unlimited number of subscriptions, so clients should do that. |
| 110 | - The `tags` array can store a tag identifier as the first element of each subarray, plus arbitrary information afterward (always as strings). This NIP defines `"p"` — meaning "pubkey", which points to a pubkey of someone that is referred to in the event —, and `"e"` — meaning "event", which points to the id of an event this event is quoting, replying to or referring to somehow. | 110 | - The `tags` array can store a tag identifier as the first element of each subarray, plus arbitrary information afterward (always as strings). This NIP defines `"p"` — meaning "pubkey", which points to a pubkey of someone that is referred to in the event —, and `"e"` — meaning "event", which points to the id of an event this event is quoting, replying to or referring to somehow. See [NIP-10](https://github.com/nostr-protocol/nips/blob/127d5518bfa9a4e4e7510490c0b8d95e342dfa4b/10.md) for a detailed description of "e" and "p" tags. |
| 111 | - The `<recommended relay URL>` item present on the `"e"` and `"p"` tags is an optional (could be set to `""`) URL of a relay the client could attempt to connect to fetch the tagged event or other events from a tagged profile. It MAY be ignored, but it exists to increase censorship resistance and make the spread of relay addresses more seamless across clients. | 111 | - The `<recommended relay URL>` item present on the `"e"` and `"p"` tags is an optional (could be set to `""`) URL of a relay the client could attempt to connect to fetch the tagged event or other events from a tagged profile. It MAY be ignored, but it exists to increase censorship resistance and make the spread of relay addresses more seamless across clients. |