Scratch

joefarebrother wrote:

the trouble is, a troll could do any of the following (imagine "lego" was a cuss word):

le[b][/b]go

l*go

le go

l-e-g-o

Let
Everyone
Go
Outside

l.e.g.o

Troubling...

Perhaps the owner of punbb-hosting should be notified as well?

cheddargirl wrote:

The Scratch Team is aware of this problem, but it isn't an easy fix. The word filter system on the forums reads things literally, so one would have to input every possible combination of BBCode usage in cuss word to prevent such cheating of the filter.

Now if there's only a way to make FluxBB overlook BBCode...

This.

slayerrobe7 wrote:

hmm i think its a good idea but the moderation team is good at what they do ive yet to see one rule broke

you're saying something, but your sig is saying something else.

wolvesstar97 wrote:

cheddargirl wrote:

Some solutions sound easier than they really are - someone would still need to program the filter for FluxBB to scan the message in preview mode. 

That would be easy- use the pre-determined script for previewing and insert it into the post script. Then have it run the filter.

If it was that easy, it would have been done already. 

Previewing just reads characters one by one and then spits out the result based on the code. In reality, what would need to happen is that you would need to create a variable so that the message is stored somewhere, then a code designed to strip BBCode goes through whatever is stored in that variable, then the censor filter is applied, and then another code reapplies the BBCode (I'm not even sure this is possible), and then the message gets posted. That's kind of a heavy and impractical way of doing it considering the forums go through about 7000+ posts a week or so.

scimonster wrote:

cheddargirl wrote:

wolvesstar97 wrote:

That would be easy- use the pre-determined script for previewing and insert it into the post script. Then have it run the filter.

If it was that easy, it would have been done already. 

Previewing just reads characters one by one and then spits out the result based on the code. In reality, what would need to happen is that you would need to create a variable so that the message is stored somewhere, then a code designed to strip BBCode goes through whatever is stored in that variable, then the censor filter is applied, and then another code reapplies the BBCode (I'm not even sure this is possible), and then the message gets posted. That's kind of a heavy and impractical way of doing it considering the forums go through about 7000+ posts a week or so.

The way the current Flux does it is to strip empty BBCodes before censoring.

And Cheddargirl said that this was an older version of FluxBB.

cheddargirl wrote:

scimonster wrote:

cheddargirl wrote:

If it was that easy, it would have been done already. 

Previewing just reads characters one by one and then spits out the result based on the code. In reality, what would need to happen is that you would need to create a variable so that the message is stored somewhere, then a code designed to strip BBCode goes through whatever is stored in that variable, then the censor filter is applied, and then another code reapplies the BBCode (I'm not even sure this is possible), and then the message gets posted. That's kind of a heavy and impractical way of doing it considering the forums go through about 7000+ posts a week or so.

The way the current Flux does it is to strip empty BBCodes before censoring.

Yeah, but aside from the fact that the current Flux version is old, even having that system in place doesn't entirely solve the problem.

I dd a little bit of research into how those systems work and it's flaws. The code that that strips empty BBCode to prevent bypassing the swear filter doesn't stop all BBCode cheating. In most cases, it's quite possible to cheat that by putting a character in it. For example, assume the word "Scratch" is on the swear filter, so:

Code:

Scr[b][/b]atch

would get caught, but

Code:

Scr[b]a[/b]tch

, will not.

True.
New idea. 
Parse the message, then use the PHP function strip_tags on it, censor that, and if it's not the same, do a warning.