Open
Conversation
Collaborator
|
I don't think a larger profanity list is desirable here - even the existing list triggers accidentally sometimes (e.g. I once got banned for mentioning "dead code" requiring manual intervention). Also only the source code gets scanned and it's not hard to hide profanity in the source code but produce it in the output image/video. Despite this we don't seem to have a problem with users even trying to send the bot profanity. |
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
2 participants
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.
Hi there!
I noticed your repository uses the
bad-wordspackage. I've recently released a new package calledno-profanitywhich is backwards compatible withbad-wordsbut contains more known profanities, and is about 150 times as fast with checking profanities.This PR should fix that!
Let me know if you have any questions