Repository navigation
Honor rfc1459 casemapping and send bot and account tags - #36
Merged
Merged
Conversation
nate[m] and nate{m} are one nick, and clients that negotiate message-tags can see +B and the sender's account without a WHOIS per member.
This was referenced Sep 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the three reports filed against irc.chonkbase.net.
CASEMAPPING=rfc1459is now what the server actually does. Nicks, channels, bans, exceptions, and channel keys fold{}|^with[]\~, sonate[m]andnate{m}are one user and#Foo[bar]and#foo{bar}are one channel. A channel registration file written before this change is rekeyed from its display name on load.message-tagsis advertised. A client can set+Bon itself (BOT=Bin005,BinWHOflags, numeric 335 onWHOIS). Clients that negotiated the capability see abottag on that user's messages. A command that arrives already tagged is still parsed, so turning the capability on does not drop traffic. Tags the client attached are not relayed.account-tagrides onmessage-tags. Those clients getaccount=<name>for a logged-in sender andaccount=*otherwise, so they no longer need aWHOISper channel member.Fixes #33
Fixes #34
Fixes #35