Combined bad words not being detected as profane.
See original GitHub issuefilter.isProfane('fuckshit') // returns false
filter.isProfane('fuck shit') // returns true
In lang.json, it has *fuck* and I was hoping that would mean anything around the word fuck would be caught like ‘gofuckyourself’, etc.
Of course, we only want to do this to certain words like fuck or shit that do not make up any other word in the dictionary: http://www.morewords.com/contains/fuck/ And, we avoid the Clbuttic mistake as well.
Any way to get it to work this way?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:12
Top Results From Across the Web
Method of Profanity Detection Using Word Embedding and ...
Therefore, in this study, we attempt to accurately identify profanity in the following two cases: (1) when Internet users use profanity by ...
Read more >How to Catch Profanity with R - Towards Data Science
These are just a few lexicons of bad words. There are many many more ready to be used. For better results, why not...
Read more >stephenhaunts/ProfanityDetector: This is a simple ... - GitHub
This is where you get a false-positive result from a profanity detector because a profanity pattern is found inside a non-profane word.
Read more >Bad Word Filter PRO - Solution against profanity and obscenity
The "Bad Word Filter" works with any language and writing system. It is easily customizable, runs on all Unity platforms and the source...
Read more >The Science of Swear Words (Warning: NSFW AF) - WIRED
So not only does English profanity tend to be pronounced with closed monosyllables, but English speakers moreover think that closed ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Currently using
patch-packageto solve the problem@bernardbaker important to consider the Scunthorpe problem when considering
includesorindexOf