nostr/nips
0
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-07-27 23:58:27 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

remove it from nip50 example too.

Browse Source
This commit is contained in:
fiatjaf
2025-03-18 13:05:58 -03:00
parent 0b3eea1053
commit 85ea8ab124
1 changed files with 10 additions and 10 deletions

2
50.md

@@ -31,7 +31,7 @@ not by the usual `.created_at`. The `limit` filter SHOULD be applied after sorti
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" }, { "kinds": [1, 2], "search": "purple" }]`. Clients may
Clients may specify several search filters, i.e. `["REQ", "_", {"kinds": [1], "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`