Add hint about client-side filtering

1 files changed, 1 insertions, 1 deletions

diff --git a/50.md b/50.md
index 470da1c..b02a3f3 100644
--- a/50.md
+++ b/50.md
@@ -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`, 
 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 
 implementation details between relays (like string sanitization, etc).