nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add hint about client-side filtering

Browse Source
This commit is contained in:
Artur Brugeman 2023-01-25 14:46:28 +03:00 committed by GitHub
parent a5a4f312cc
commit d534df39c0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
50.md
View File

@ -28,7 +28,7 @@ a `NOTICE` to inform the client. Future NIPs will specify behavior for other eve
A filter matches if one of the provided `keywords` matches. Each keyword string may contain several conditions - `words`, A filter matches if one of the provided `keywords` matches. Each keyword string may contain several conditions - `words`,
all the words must match for a keyword to match. The meaning of `words` depends on event kind. all the words must match for a keyword to match. The meaning of `words` depends on event kind.
Clients SHOULD use the supported_nips field to learn if a relay supports keyword filter queries. Clients SHOULD use the supported_nips field to learn if a relay supports keyword filter queries. Clients MAY send keyword filter queries to any relay, if they are prepared to filter out extraneous responses from relays that do not support this NIP.
Clients SHOULD query several relays supporting this NIP and specific kind to compensate for potentially different Clients SHOULD query several relays supporting this NIP and specific kind to compensate for potentially different
implementation details between relays (like string sanitization, etc). implementation details between relays (like string sanitization, etc).