I have not written or used and profanity filters, but this module might help you.
Regexp::Common::profanity -- provide regexes for profanity [metacpan.org ]

How about a filter which points out the words that need to be removed before the post can be made?

How about a filter which points out the words that need to be removed before the post can be made?

Do you mean as an entire alternative to ### substitution, without resorting to “this post is being held for moderation” * ? Then you're just encouraging the user to go hunting through their lookalike characters in order to be clever and slip ### past the filter. But that's a whole different thread.


* So that by the time it's approved and posted, the whole discussion has moved on, and you feel like an idiot for saying something that would have fit right in last week.

No, its like when you submit a form and you use a word you shouldn't use, upon submission you are informed that you said a nono, it will tell you which form field and what words need to be fixed. like
The following word(s) were found in username field and must be removed before you can submit:
Foo, bar, etc

Here it is. I have removed some words because I did not want to offend anyone.

In @badwordsa is the list of words that no matter how they appear in a sentence or try to hide them in another word, you will find that sequence of words only appear once in the dictionary which means that array doesn't have to contain every word in the book.

In @badwordsb are the words that might appear in another word, for example the word ass also appears in pass, bass, amass, etc, so the combinations must be listed one by one, which presents not problem. I know it is possible to make this work better and welcome any input.

The best part is NO bad words make it to the post so that the reader doesn't have to use his/her imagination trying to figure out what the word actually was (yes, there are many people who waste time pondering). That said, here it is:

my @badwordsa=('#*$!','damn','piss');
my @badwordsb=('#*$!','asswipe','asskisser','asskiss','kissass','kiss ass','hell');

foreach $c(@noninsertables){ #check personal (alias) name for fowl language
foreach $d(@insertables){
if (($name =~ m/\b$c\b/im || s/\W//g)||
  ($name =~ m/$d/im)){
   $ec3 = 1;
   $te++;
      }
  }
}

if($ec3 == 1){print"      <li>&nbsp;The Following Bad Words Were Found In The Name Field And Must Be Removed:</li>\n";}#end alias
foreach $d(@noninsertables){
if($name =~ m/\b$d\b/im){
print" <span class=\"l\"><span class=\"rs\">$d</span></span>";}}
foreach $c(@insertables){
if($name =~ m/$c/im){
print" <span class=\"l\"><span class=\"rs\">$c</span></span> ";}}
    
    

I tried to find the original post where I had asked for help putting this together but I'm pretty sure the real credit goes to phranque or rocknbill, can't remember exactly but they have set me straight on more than one thing in perl and only right that credit goes where its due

Forgot to mention, repeat for each field using different vars for each field. $ec was supposed to mean error code so I just added a different number to the end for each field.

Same @array used for all fields

Like @lucy24 said, though, my problem lies with people that actively try to get around it. I guess they just insist that their point can't be made without the profanity or vulgarity? I currently filter it with ****, which is fine for the wide majority, but there are always a handful of people that insist on using unexpected characters.

And if I alerted them to something being filtered, it would just make it easier for them to keep trying until they get it go through. These people would make a game of it.

For example, today I had "g0d@mm" to pass.The user intentionally swapped the o with a 0, the a with an @, and then added a second m instead of an n.

A few days ago, another user intentionally submitted "Þµš$¥".

So I guess that what I need is a list of every possible character that could be used to look like another character, convert each of them to the corresponding alpha character, then filter for profanity, then convert it back?

You could block entire unicode ranges, like the characters whose sole function is to look like some other letter. (Back when you could see search queries, I would see these in searchers from Japan who apparently laboriously typed in one lookalike after another, and then the poor search engine had to figure out what they meant.) Sorry, users, you're not allowed to say anything in Greek or Russian.

No matter what you do, you'll get false positives, like when the present site throws a fit if you have occasion to enter any common Thai name. (Not the ones that end in -korn. The ones with the other consonant.)

It may be more useful to look at patterns. There are really not many legitimate configurations even of {alphabetic} {non-alphabetic} and still fewer of {non-alphabetic} {alphabetic} in that order, while {alphabetic} {non-alphabetic} {alphabetic} can be reduced to a short list of specific patterns. Adjacent letters and numbers is another easy one. (I check for those when proofreading ebooks, though there it's to catch OCR glitches rather than willful malice.)

So, how do we make a filter that won't allow misspelled dictionary words. Oh my, that means people would have to act civilized.

Do you have a reason for not disallowing special characters, other than in an email field ?

The only applicable time that I see them is when someone copies an article from a news site that has a different encoding. So ‘ ’ “ ” are relatively common. And of course, regular punctuation.

Can you suggest a way that I could search my database for special characters, to see how often they're actually used? And if they're rare enough, is there an easier way to block them than:

if ($text =~ /[^\w\s\n\r!@#$%\^&\*\(\)_\+\-=\[\]"';:<>\?,\.\/]) {
 # allowed
}

else {
 # contains special character
}

<tangent>

\s\n\r

That's redundant. \n and \r (also \t, nbsp and so on) are all \s characters. And, further along, _ (lowline) is a \w character.
</tangent>

You shouldn't need to escape anything other than brackets [ ] (“square brackets” in some dialects) and hyphen - inside grouping brackets. And \ backslash, though I don't think you have one. (And probably don’t need one, since it doesn't occur naturally.) Not sure about non-initial ^ though there you could always play it safe.

Where you have ' " you should really have ' " “ ” ‘ ’ to allow for curly quotes. Some people have their systems set up to substitute them automatically; other people--ahem! cough-cough!--enter them manually. The same probably applies to — (dash) substituted for -- double hyphen. Oh, and … for ... three dots.