BadWordsFilter set to true, but still coming through

whelman · Post by **whelman** » 04 Jul 2006, 15:05

We've set our BadWordsFilter paramater to true, but it seemingly has no affect. Is there anything else that needs to be done in the config file? Anyone else experiencing this issue?
Thx.

Post by **Lapo** » 04 Jul 2006, 17:27

A restart is necessary after the config change.
Did you do it?

whelman · Post by **whelman** » 05 Jul 2006, 14:54

Yup. But still nothing.

Post by **Lapo** » 05 Jul 2006, 15:23

The badwords filter works with public messages, user names and room names so if you send a text containing a bad word in your list you should see it filtered and get an admin message based on your settings.

I did a very basic test:
-> started SFS 1.4.0 with the filter turned on
-> Typed "oooh shit!" in the Advanced Chat example
-> got an admin message and the message sent was turned into "oooh ****!"

So, I can't see why it's not working for you.
If you can't make this simple thing work, then I will need to know all the details of your OS, JRE, and config.xml

whelman · Post by **whelman** » 05 Jul 2006, 15:46

OK. Figured it out.
1. It's case sensative.
2. It only filters for other clients, not your own (at least in our implementation, but I think that may be unique to us)

Thx.

Post by **Lapo** » 05 Jul 2006, 16:17

1. It's case sensative.

No, it's not. Bad words are recognized in any case. Example: "ShiT", is recognized.

2. It only filters for other clients, not your own (at least in our implementation, but I think that may be unique to us)

nay, if you are all alone in the chat and type a bad word it will be filtered

whelman · Post by **whelman** » 19 Jul 2006, 18:28

Yes, bad words are still filtered on the server, but our client doesn't show it for the user who is doing the swearing, only others - that's just our implementation.

Does the filter catch partial words? It seems we are getting filtered for words like "assume" because "ass" is a bad word. Is there any way to limit the filtering to entire words?

thx.

mnkyhead · Post by **mnkyhead** » 19 Jul 2006, 20:36

It seems we are getting filtered for words like "assume" because "ass" is a bad word. Is there any way to limit the filtering to entire words?

Yea I was going to ask the same question.

Post by **Lapo** » 20 Jul 2006, 08:31

Does the filter catch partial words? It seems we are getting filtered for words like "assume" because "ass" is a bad word. Is there any way to limit the filtering to entire words?

I see your problem. This is actually a particular case in which the filter may fail. The filter tries to catch bad words stripping spaces and punctuation in order to be more effective.
It would be probably better to add a flag in the main config file to allow toggling this feature.
I've added this in our to-do list

mnkyhead · Post by **mnkyhead** » 21 Jul 2006, 18:17

Yea I think the filter needs a little work, I was going through the chat logs, and found this

ZOEY said: it w** *ome lady

Post by **Lapo** » 22 Jul 2006, 07:44

Yep, that's exactly because of the same reason explained above.
By stripping the punctuation, the filter can catch bad words hidden within other characters, like ... _s_h_i_t_ etc...

"Ass" is a very short bad word that can be part of hundreds of other words ("mass", "pass", "passive", "passion" and zillions more...)

Until we add the new flag it's probably recommendable to avoid filtering very short words that can be easily found in other longer words/phrases.

BadWordsFilter set to true, but still coming through

BadWordsFilter set to true, but still coming through

opps