• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Censoring Mistake?

Unfortunatly, there is a way around the vulgarity checker and you can put all the curse words you want in the posts.

double unfortunatly, they have known about this issue and have yet to correct it.

Ah well,

PF
 
Correct me if I'm wrong, but they'd have to parse the text at a different time to fix that issue, right?
 
Possessed there is nothing to correct, there are two options in the admin of the product. Loose word matching or full matching. We use loose. Why? Well as you have probably seen on other forums the word $hit is banned. So when you type in matsushitsu, the checker says you've entered a banned word. We choose not to do that to users, and hope most users are mature enough to abide by the rules, if not they are dealt with by mods.
 
I am talking about the ability to go bypass the checker and put in curse words without surrounding letters.

example

shit

not matsushitsu
 
Freak 🙂 You aren't getting what I'm saying. It's on loose mode right now which only scans _word_ or _word or word_ not word<CR> or word. or word, If we wrote an algorithym to do it (which we could) it would lengthen post times to at least twice as long. So once again it is working just fine as its meant to be that way. If the admins/mods want full word scanning then that's their choice. Capiche?
 
Back
Top