From 57d758b07fbe7d3bf95558c93abdbd9eef6a9b42 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luiz=20Pican=C3=A7o?= Date: Fri, 27 Jan 2023 21:15:00 +0000 Subject: [PATCH] Fix NIP-50 typo --- 50.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/50.md b/50.md index ea9eb5db..5bda3559 100644 --- a/50.md +++ b/50.md @@ -29,7 +29,7 @@ matching against other fields if that makes sense in the context of a specific k A query string may contain `key:value` pairs (two words separated by colon), these are extensions, relays SHOULD ignore extensions they don't support. -Clients may specify several search filters, i.e. `["REQ", "", [{"search":"orange"},{"search":"purple"}]`. Clients may +Clients may specify several search filters, i.e. `["REQ", "", { "search": "orange" }, { "kinds": [1, 2], "search": "purple" }]`. Clients may include `kinds`, `ids` and other filter field to restrict the search results to particular event kinds. Clients SHOULD use the supported_nips field to learn if a relay supports `search` filter. Clients MAY send `search`