Skip to content

Conversation

@slingamn
Copy link
Contributor

@slingamn slingamn commented Dec 7, 2025

I brought this up in #ircv3 but I wanted a "written" discussion. IMO, the requirement for the server to filter RPL_WHOISKEYVALUE does not make sense:

  1. It seems to assume that clients will display raw keys and values directly in the whois output. But in fact, even key names will require individual client support (to translate the internal identifier into something user-readable). The correct place for this filtering is on the client side, where the client can display the keys and values it understands and ignore the others.
  2. The goal of controlling the size of the WHOIS response is subsumed under controlling the total size of user metadata, for which FAIL METADATA LIMIT_REACHED has been specified (we could probably use some non-normative implementation recommendations on setting limits)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant