You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had an issue with my blacklist matching simple words as offensive and then i went into digging the issue and find out that the profanity validation is not working in the same way as filter.
Profanity validation is working with a simple "stripos" function
but filter is working with regex (preg_replace_callback) which makes a big difference when your blacklist has some words that can be found in simple words.
I think the validation should work in the same way as filter so blacklist have the same result in either way.
The text was updated successfully, but these errors were encountered:
Speaking of Blacklists, I think there should also be a Whitelist. For example, I have my config to "replaceFullWords" => false; Meaning something like "MF" the full word 😅changes to Mother%$^er, however, this also means "Assignment" becomes @#$ignment. Maybe a whitelist would do this package some good, where I can set a list of words that should be ignored.
I had an issue with my blacklist matching simple words as offensive and then i went into digging the issue and find out that the profanity validation is not working in the same way as filter.
Profanity validation is working with a simple "stripos" function
but filter is working with regex (preg_replace_callback) which makes a big difference when your blacklist has some words that can be found in simple words.
I think the validation should work in the same way as filter so blacklist have the same result in either way.
The text was updated successfully, but these errors were encountered: