Hi MiniBB Team,

It's me again ;-)

I have another request, could be easy, might be tricky. I need to be able to censor certain words when someone posts. How hard would it be add this feature ? Could I add a text file into the miniBB directory with a list of banned words which the script checks the post against and replaces it with a global word instead ???

This feature is pretty common on cgi forums, I think it would make your forum move attractive for developers (+ I can't use this without it !).

Thanks again.

Jon

Yeah i think it will be added in miniBB 1.1. It's pretty simple I'll make this feature today. We've already added list for "bad" usernames in miniBB 1.1

Do you have an estimate of around when the new version will be released?

I need to launch my forums in sync with the new layout for my site, and I want to launch with version 1.1..

Jeremy
How do you realize bad words protection? I think, it is really not necessary function, because of 2 things:
1) I am personally (as author :) against censorship. If the poster uses S-words, it is his ethics problem, and everyone of us knows what S-words mean, so the censorship is simply stupid.
2) Even if you have a list of S-words, I can always use "new modifications" :). F.e., if you have words "fuck" and "shit" disabled, I can use fUck, SHIT, $hit etc, etc. It is simply impossible to check every word.

At least, ban exists for solving this problem...

I know that it's virtually impossible to stop it entirely, but it gives us a chance of stopping most of it, and everytime a user thinks up a new workaround we'll see it and add it to the badwords.txt file.

Is this feature in place now ??

Jon

yes, but its still very very hard to get all the workarounds. They can not only make workarounds such as Æuck (not recognised as a normal f), they even make it appear as the normal word, yet the filter will not pick it up. like for the word fuck, you can just write [ b ]f[ /b ]uck (enclosed in B tags), and the filter wont pick it up, yet it will appear as the normal word.

So it really is incredibly hard to stop, or even slow down. People will swear when they want to, this wont stop them at all. All you need is tight rules on your forum about swearing, if you view your forums enough you can issue warnings to the people that swear (and edit their posts), and if they repeat it then you can ban them. (if you take it that seriously that is)

filters never stop anyone, If you want to swear on a board you just do a workaround, you don't generally just decide not to if the filter picks it up as a swear word.

I agree with paul, I don't really want the censoring feature, I have no need for it.

unfortunately it's part of the brief to use a forum with this feature. This is because the local education authority have paid for the site and they are VERY worried about kids using the net and being approached by Peodphiles, bad language etc. They would shut us down !

Hopfully most of the kids (16 and under mostly) won't be aware of using BB code to do work arounds.

I agree that if this was a adult forum then no worries, people can be trusted to be polite and if they're not they get banned.

Ta

Jon

Ok, I've got the bad words filter set up and it's working fine.

Except for when users put the words in quotes i.e. "shit", "ass" etc, etc.

Is there a way for the quotes NOT to defeat the bad words filter?

I have enabled the bad words filter and now when a post is made this appears:

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi_replace(): REG_BADRPT in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 21

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php:15) in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/index.php on line 226


Any ideas on how to fix it? The post is made, and can be found, but that is what comes up after you post.

jdmarti1
Check you badwords.txt file. THERE MUST BE NO ENDING LINE AFTER LAST WORD! (RTFM)

Anonymous
There is no that way.

Team,

I read the fuck!ng manual. I even checked the damn badwords.txt file. The problem still exists - Here is what I get when posting something that is in the list:
Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: eregi(): REG_EPAREN in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php on line 15

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/magicwisp.com/httpdocs/forums/badwords2.php:15) in /home/httpd/vhosts/magicwisp.com/httpdocs/forums/index.php on line 226


It does seem to correlate to the number of bad words I use in the post. I am sure I did something wrong, I am just not sure what it is.

Could you post here a list of badwords you are using?

son of a bitch
sonofabitch
doggiestyle
doggystyle
jackasses
wetbacks
fucktard
biotchin
jack ass
oral sex
anal sex
oralsex
jackass
analsex
blowjob
fucking
asshole
wetback
fisting
bitches
niggers
fucker
fucked
faggot
biotch
nigger
niggas
biatch
bitchy
bitch!
nigga
shitty
bitch
chink
pussy
fuck
dick
cunt
shit
cock
fags
fag
cum

Strange - I've tested on my server and everything seems to work ok...

But first of all, don't use spaces in defined words - it will not work, and it is not necessary in general. "Anal sex", for example, definitely is not the "s" word, but a term. In this case, you either need to prohibit the word "anal" or the word "sex". For prohibiting entire phrases, use Flood filter plugin.

Check that after word "cum" there is no newline or space.

The same for many another words...
It should be simply "jackass" not "jackasses".
"wetback" not "wetbacks"
Simply defining "fuck" is enough - "fucking" will be replaced to "****ing" etc.