Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make MONITOR more compatible with blackbox casefolding? #1083

Closed
slingamn opened this issue May 28, 2020 · 1 comment
Closed

make MONITOR more compatible with blackbox casefolding? #1083

slingamn opened this issue May 28, 2020 · 1 comment
Milestone

Comments

@slingamn
Copy link
Member

Something I've been thinking about is that to the maximum extent possible, clients shouldn't have to be aware of casefolding. In other words:

  1. Clients should be able to treat all nicknames and channel names as opaque byte strings
  2. We should always send the canonical (unfolded) form of the identifier
  3. Folding should be thought of primarily as a

In the case of MONITOR, MONITOR L sends the folded identifier. It might be better to send the form the client originally sent.

@DanielOaks
Copy link
Member

Makes sense 100%. canonical forms being sent to clients always is optimal for sure~

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

No branches or pull requests

2 participants