We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
version: 0.12.1-dev
Using characters known to be markdown control characters in irc nickname must not be parsed as markdown control character by discord.
Using a character known to be a markdown control character in irc nickname makes discord parsing the nickname.
Join an irc channel bridged to a discord one, and use this nickname:
`test
Then types this message in irc channel:
this is code`
You get that on discord side:
<test> this is code
test> this is code
You must get that:
<`test> this is code
I guess any character known to be a markdown markup one must be escaped when found in irc nickname prior to be sent to discord.
The text was updated successfully, but these errors were encountered:
41aa8ad
Fixed this by adding a new StripNick parameter, which strips every non-alphanumerical character.
Sorry, something went wrong.
No branches or pull requests
Which version of matterbridge are you using?
Please describe the expected behavior.
Using characters known to be markdown control characters in irc nickname must not be parsed as markdown control character by discord.
Please describe the actual behavior.
Using a character known to be a markdown control character in irc nickname makes discord parsing the nickname.
Any steps to reproduce the behavior?
Join an irc channel bridged to a discord one, and use this nickname:
Then types this message in irc channel:
You get that on discord side:
You must get that:
I guess any character known to be a markdown markup one must be escaped when found in irc nickname prior to be sent to discord.
The text was updated successfully, but these errors were encountered: