Allow / in nicknames to support common IRC bridges.
#11
Conversation
This file contains 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
This character is used by IRC bridges that follow the proposed IRCv3 spec at <ircv3/ircv3-specifications#417>, such as Matterbridge and PyLink. Not accepting the character leads to messages being dropped silently.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The forward slash is used by IRC bridges that follow the proposed IRCv3 spec at ircv3/ircv3-specifications#417, such as Matterbridge and PyLink. See for example Materbridge example configuration
Not accepting the character leads to messages being dropped silently, which very is confusing and looks like you're missing half the conversation.
The proposal was ultimately not accepted as an IRCv3 draft but it is being used in the wild and there's no downside to being compatible with it because
/is not a special character the protocol.