please ease up on the language filter
please ease up on the language filter
There have been many complaints about the language filter and how it handles words. It would be a great improvement to take spaces into consideration (eg: "as someone") as well as leaving words containing bad words (like "assets").
I've been told that putting a space at the begining or the end of the bad word in the the bad word list would fix the second problem.. but It ended up not detecting any words at all, including the ones which matched.
Please consider this in the future release.
I've been told that putting a space at the begining or the end of the bad word in the the bad word list would fix the second problem.. but It ended up not detecting any words at all, including the ones which matched.
Please consider this in the future release.
nature has a funny way of breaking what does not bend
Yes, this has been mentioned several times in this board. We have plans for adding more flexibility to the bad word filters.
Additionally I'd like to mention that, with the latest version of the server, we enhanced the "pubMsg" internal event. It is now possible to catch all the public messages in your extension and apply your custom filters.
Additionally I'd like to mention that, with the latest version of the server, we enhanced the "pubMsg" internal event. It is now possible to catch all the public messages in your extension and apply your custom filters.
And while we talk about suggestions....
This one one may be will not be included in the to-do list but I think its interesting.
What about flag option? When some chat is flaged it's send to moderator to take adctions. And the bad words fillter can just do this task automatically - sends the message to moderator so it could take the proper actions.
This one one may be will not be included in the to-do list but I think its interesting.
What about flag option? When some chat is flaged it's send to moderator to take adctions. And the bad words fillter can just do this task automatically - sends the message to moderator so it could take the proper actions.
-
turtlesoup
- Posts: 77
- Joined: 28 Dec 2007, 20:56
Lapo wrote:Yes, this has been mentioned several times in this board. We have plans for adding more flexibility to the bad word filters.
Additionally I'd like to mention that, with the latest version of the server, we enhanced the "pubMsg" internal event. It is now possible to catch all the public messages in your extension and apply your custom filters.
Does the pubMsg extension get called before or after the word filter? Or does it disable the word filter?
I just tried creating my own custom filter. The word filter comes first before pubMsg and it does not disable the word filter. When I typed in a bad word that is listed inside SFS bad word list and my custom filter, SFS catches it first.Does the pubMsg extension get called before or after the word filter? Or does it disable the word filter?
-
turtlesoup
- Posts: 77
- Joined: 28 Dec 2007, 20:56
darnpunk wrote:I just tried creating my own custom filter. The word filter comes first before pubMsg and it does not disable the word filter. When I typed in a bad word that is listed inside SFS bad word list and my custom filter, SFS catches it first.Does the pubMsg extension get called before or after the word filter? Or does it disable the word filter?
Cool. Thanks!
just a suggestion.
use a client side word filter like mine.
it wont ban or kick but it will remove a lot more bad words, and its has a ignore word list (ignore grape but remove rape)
checkout the link bellow for source
http://m0rkeulv.net/showsource.php?file=/code/filter.as
use a client side word filter like mine.
it wont ban or kick but it will remove a lot more bad words, and its has a ignore word list (ignore grape but remove rape)
checkout the link bellow for source
http://m0rkeulv.net/showsource.php?file=/code/filter.as
-
turtlesoup
- Posts: 77
- Joined: 28 Dec 2007, 20:56
For now, this is what I'm doing. The client is running a RegEx type thing to filter out bad words and then taking the appropriate action.no-one wrote:use a client side word filter like mine.
Hopefully SMS does this soon. Using regular expressions pretty much fixes any problems with the "ass / pass" type things.