I'm in the process of making a highly sensitive cuss word filter block. As it is now it can detect 6 cuss words (this includes the big three) and lots of different work-arounds of those cuss words. For the sake of example just assume that “cake” is a cuss word.

If you typed “c a k e” (note the spaces between the words) and ran it through the block it would not allow the post to go through.

If you typed “cak” it would block it

If you typed “ca ke” it would block it

If you typed “c ake” it would block it

If you typed “cak e” it would block it

Note: All special characters such as “*”, “$”, “#”, etc. are not allowed. This is too avoid easy work-arounds. They can work around it by typing letters in between, but it looks much less obvious when it is surrounded by other letters. It's almost like it forces the person to camouflage their own cuss word xD

It's best not to say what it can't do, that had might as well not be known by the few who may want to exploit it as much as possible. But basically all normal work-arounds are covered. No problem.

So I just want to know if I'm missing anything crucial. Please post your suggestions, they'll be helpful. Thanks!

oh yah, should I censor “hell” and/or “*”?

haha, that star surrounded by quotes is “c r a p”, should that be censored? (obviously it should be because the forums censored it, lol)

May as well release all it's capabilities if you are going to release the project. If you release the project, it'll all be public anyways.

Also, while I don't find the “c” word as a cuss word, some do, so it would be good to add it.

I've released another version already, but I'll add the “c” word for good measure

bullelk12 wrote:

I've released another version already, but I'll add the “c” word for good measure

Does your project have hashing? Otherwise people can see all the cursewords by pressing “see inside”

And I would censor all cursewords, half-cursewords, mean words (like loser) , etc.

the actual curse words aren't obvious because there is no full cuss words visible. It's not a problem

pugluv4ever wrote:

bullelk12 wrote:

I've released another version already, but I'll add the “c” word for good measure

Does your project have hashing? Otherwise people can see all the cursewords by pressing “see inside”

And I would censor all cursewords, half-cursewords, mean words (like loser) , etc.

I beg to differ, “mean words” like loser are important for other sentences. Other than very vulgar words I am one to think that words such as “c r a p”, “loser”, “stupid” are not “bad” enough to block. In my honest opinion swearing is the least offensive thing on the planet, and words being “bad” is taught/learned, not instinctual. Since this is Scratch, though, I guess you'd have to block “pure” swear words. But not things like stupid, loser, dumb, or anything. Sometimes some people just have to learn that being called “dumb” isn't the end of the world

Can't wait to see the final product anyhow. Adios.

Yea, I agree with you. I've already taken “c r a p” away in my latest version (not yet released) because it was causing too many words to not be accepted. And someone should be able to take being called stupid sometimes, as you said it's not the end of the world. Plus, you can be called stupid on the scratch forums just as easily, the only worry is that no one will do anything about it for chat rooms. Well, those who are worried about it can just not use chat rooms. In the end, if they get called stupid, they can deal with it. Now, cussing at someone is a bit different, but that is what this is for. It's not perfect yet, but it will be pretty close by the time I'm done with it.

btw, I'm only going to censor cuss words and I won't censor medium words. Because the more words I try to block to more likely my filter is to block a normal word, so sorry, I can't cover “idot” “stupid” “moron” etc. Those will have to be moderated by the chat room moderator.

Right now, it's not very helpful because there are no cloud lists or letters in cloud data but maybe if they allow them

There is a problem. You can for example say ‘You are crab’ with the typo b instead of p. Since crab is not a swear word, people would still be able to say it.

Malthetalthee wrote:

There is a problem. You can for example say ‘You are crab’ with the typo b instead of p. Since crab is not a swear word, people would still be able to say it.

well, actually it would and “cr ap” isn't covered by that version. But I'm not going to include “cr ap” as a cuss word anyways. Because the more words that I have the filter go through, the more sensitive my filter is. And the more sensitive my filter is, then the more often it will think a normal word is a cuss word. So I have to find an even balance

Well you can't really swear but I have seen some that came out perfectly and everyone on that page saw it.

Pretty much any cuss word filter that I can think of is likely to have inappropriate content (the words) that can be viewed by anybody that viewed the inside of the project - so I don't recommend making projects with that. That's the reason that we require any chat projects that use cloud data to use a “white list” filter that only allows words that are on the “allowed words” list to be used.