diff options
| author | Luiz Picanço <lpicanco@gmail.com> | 2023-01-27 21:15:00 +0000 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-02-01 07:06:25 -0300 |
| commit | 57d758b07fbe7d3bf95558c93abdbd9eef6a9b42 (patch) | |
| tree | e610501f7c06f45bcfbf775879270ece4e2ad4b6 | |
| parent | 3b1cd96798a9c6b6607b01814b31266dc41934f0 (diff) | |
Fix NIP-50 typo
| -rw-r--r-- | 50.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -29,7 +29,7 @@ matching against other fields if that makes sense in the context of a specific k | |||
| 29 | A query string may contain `key:value` pairs (two words separated by colon), these are extensions, relays SHOULD ignore | 29 | A query string may contain `key:value` pairs (two words separated by colon), these are extensions, relays SHOULD ignore |
| 30 | extensions they don't support. | 30 | extensions they don't support. |
| 31 | 31 | ||
| 32 | Clients may specify several search filters, i.e. `["REQ", "", [{"search":"orange"},{"search":"purple"}]`. Clients may | 32 | Clients may specify several search filters, i.e. `["REQ", "", { "search": "orange" }, { "kinds": [1, 2], "search": "purple" }]`. Clients may |
| 33 | include `kinds`, `ids` and other filter field to restrict the search results to particular event kinds. | 33 | include `kinds`, `ids` and other filter field to restrict the search results to particular event kinds. |
| 34 | 34 | ||
| 35 | Clients SHOULD use the supported_nips field to learn if a relay supports `search` filter. Clients MAY send `search` | 35 | Clients SHOULD use the supported_nips field to learn if a relay supports `search` filter. Clients MAY send `search` |