fix: special messages can prevent triggering a ChannelMessageEvent #513
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
:req Invalid CAP command, :tmi.twitch.tv CAP * ACK :, and PING :tmi.twitch.tv Co-authored-by: Sidd <iProdigy@users.noreply.github.com> Co-authored-by: SubSide <SubSide@users.noreply.github.com>
iProdigy
approved these changes
Jan 18, 2022
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.
Prerequisites for Code Changes
Issues Fixed
user messages containing one of three special strings are able to circumvent parsing into a channel message event and could potentially bypass moderation features built with twitch4j.
Additional Information
Thanks to @SubSide for reporting the issue.