diff options
| author | Semisol <45574030+Semisol@users.noreply.github.com> | 2022-07-26 04:33:33 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-26 04:33:33 +0300 |
| commit | 1b94488742494d8f9f3d2fefc908e6541562ca39 (patch) | |
| tree | 5a3f2e09d5d847081fd4df7eed2d6ba99fddf09b | |
| parent | 140d48e4e95535ca9e3b99e2de93165096f3bc10 (diff) | |
nip16: small fix
| -rw-r--r-- | 16.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -21,7 +21,7 @@ Upon an ephemeral event being received, the relay SHOULD send it to all clients | |||
| 21 | Client Behavior | 21 | Client Behavior |
| 22 | --------------- | 22 | --------------- |
| 23 | 23 | ||
| 24 | Clients SHOULD use the `supported_nips` field to learn if a relay supports generic tag queries. Clients SHOULD NOT send ephemeral events to relays that do not support this NIP; they will most likely be persisted. Clients MAY send replaceable events to relays that may not support this NIP, and clients querying SHOULD be prepared for the relay to send multiple events and should use the latest one. | 24 | Clients SHOULD use the `supported_nips` field to learn if a relay supports this NIP. Clients SHOULD NOT send ephemeral events to relays that do not support this NIP; they will most likely be persisted. Clients MAY send replaceable events to relays that may not support this NIP, and clients querying SHOULD be prepared for the relay to send multiple events and should use the latest one. |
| 25 | 25 | ||
| 26 | Suggested Use Cases | 26 | Suggested Use Cases |
| 27 | ------------------- | 27 | ------------------- |