Hello Jackson,

These spammers are getting smart these days and I don't think censoring words would make sense. For instance if you are censoring "fuck" and "you", it wouldn't replace anything if the user typed in "fuckyou". It's still offensive

Hi Mark,

You are not telling me the F word right?

What I'm trying to say is, since adding keywords to censor is allowed, if the censoring is done by word/s. Admins can just enter multiple variations of that keywords, like "**** you, fuckyou,fucku,fuck" which is what I did. In my understanding of what you are saying, there's no need to make variations on the censor keyword since Komento will just search for it in each word and censor it. That way also affect valid word like in my example above: "class" becomes "cl***" when a sensor keyword is "a s s".

Thanks,

Jackson

Hello Jackson,

Ah, no it was just an example (Hope that you don't take it offensively)

The problem is actually when you enter too many words to censor I seen sites where they are censoring over 10,000 words and such word processing is very taxing on the cpu. Most of the time, the php script would just time out as it needs to go through 10,000 loops to censor these texts.

Hi Mark,

I know I'm just kidding.

Well, it's just my two cents regarding Word Censoring. Something to think about moving Komento forward. I'm sure you guys will be able to come up with solution. The current censoring of keyword I believe is not properly doing it.

Thanks,

Jackson

Hello Jackson,

I am sorry for the delay of this reply as it is a long weekend off for us here. Noted, will keep an eye on this We need to strike a balance between performance vs functionality though.