ADMIN - Only admins can set channels +L
ALL - All users can set channels +L
CHANOP - Controls who can set a channel +L
IRCOP - Only IRCOps can set channels +L
LOCAL - Local filtering options
NONE - Turn off channel filtering
REMOTE - Remote filtering options
SA - Only Services Administrators can set channels +L
These commands set the levels for the filters as well as who can add the filter mode for channels (rooms). A room filter mode is +L and can be added by either a network operator, services admin, or server admin. Also it sets whether all messages will be filtered or only some messages. The local setting will have it filter messages only on your server, whereas remote will cause it to filter all messages regardless of their origin on the network.
Example:
/as help filter channel <topic>
If warn is off, people might not realize when they are being censored or having their messages dropped. Even with warn on they will not be told which word triggered the filter, but unless you have unusual filters it should be fairly obvious. But the warning gives them an opportunity to rephrase their message until it can get through completely.
This will list all the filtered words on the server as well as all the configuration settings.
Example:
/as filter list
Use this command to check how the filters are set. It will probably give a moderately long list if you have several banned terms. You can also use filter word list to just list which terms are blocked by the profanity filters.
ORIG - Map the character back to its default mapping
SELF - Map character to itself
STOP - Create a stop character
This will cause a character to be mapped as a letter before checking for profanity. You can do: /as filter map '3' self Which causes '3' to map to itself. /as filter map '3' stop causes '3' to be a stop character. /as filter map '3' orig Causes '3' to restore its original (default) mapping. The use of the number 3, for example, could map to the letter e so if someone says l33t and leet is on your list of prohibited word it would prevent the word from showing.
Example:
/as help filter map <topic>
Mapping can prevent the most common forms of profanity that include common substitutions.of numbers for various letters. But you can customize it for whatever you find yourself having problems with.
ALL - All messages will be filtered
LOCAL - Only local messages will be filltered
NONE - No messages will be filtered
REMOTE - Only remote messages will be filtered
SOME - Filtering depends on user and channel settings
This will define what should be filtered. For example /as filter message all would filter all messages. While /as filter message local warn on would send a warning locally that the word being used is not acceptable. If you decide to censor instead of drop then it will show the unacceptable text replaced with asterisks.
Examples:
/as help filter message <setting>
This works in the same basic way as filter channel except it affects how private messages are filtered rather than rooms.
This creates the list of text that will trigger the profanity filters. This will add, delete and list prohibited words on your server.
ADD - Add a word to be filtered
DEL - Stop filtering a word
LIST - View the list of filtered words
Example:
/as help filter word <topic>
The exact strings will be filtered and any text that matches them when mappings are taken into consideration. See FILTER MAP. But profanity filters are only designed to teach users what is acceptable on your server. People could always a find a cleverer and cleverer way to get around them and banning broad strings of text will hit many harmless conversations. So true monitoring should always be done by people.