FILTER

Usage: FILTER <command> [<parameters>]

The filter command provides a method to prohibit words in the list by displaying asterisks *** in a room, or private message instead of the forbidden word. The server can also be set to keep any message that contains a banned term from being sent at all instead of just censored. The room or the user must be mode +L unless the server is set up to filter everything.

CHANNEL - Set filter level.

LIST - List current settings in the filter command.
MAP - Map character.

MESSAGE - Filter messages level.

WORD - Add a word to the filter list

Example:

/as help filter <command>

These are the commands to control profanity filtering. This will allow you to determine which things may not be said on your network or may not be said in certain places. Filtering will only ban the exact text that you enter. This is designed to prevent people from accidentally using language that you consider to be inappropriate and to help them learn what is acceptable. 
If users want to get around the filter, they probably can find ways to do so. But more generic filters would also ban numerous forms of acceptable speech. This is why humans should monitor rooms for unacceptable language if it is important that the rooms be clean. Only a human can tell the difference between things such as "bigass" and "grass".

Usage:FILTER CHANNEL <setting> [option]

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.

Usage: FILTER CHANNEL ADMIN

This command controls who may set a room to be filtered for profanity. It can be set to ALL, NONE, CHANOP, IRCOP, SA, or ADMIN. If it is set to all then all rooms will be filtered. If it is set to none then no rooms will be filtered. The admin option causes only +L rooms to be filtered and only allows server admins to set a room +L..

Example:

/as filter channel admin

This is a good setting if you want censorship to only be set rarely and by people you trust a great deal.

Usage: FILTER CHANNEL ALL

This will cause all text in all rooms to be filtered unless specifically specified otherwise in the LOCAL or REMOTE settings.

Example:

/as filter channel all

This is useful for networks that want to monitor profanity as much as possible.

This command controls who may set a room to be filtered for profanity. It can be set to ALL, NONE, CHANOP, IRCOP, SA, or ADMIN. If it is set to all then all rooms will be filtered. If it is set to none then no rooms will be filtered. The chanop option allows the room operators to set their rooms +L..

Example:

/as filter channel chanop

This gives control over profanity filtering to the people who run the room. This is ideal for a less restrictive network.

This command controls who may set a room to be filtered for profanity. It can be set to ALL, NONE, CHANOP, IRCOP, SA, or ADMIN. If it is set to all then all rooms will be filtered. If it is set to none then no rooms will be filtered. The ircop option causes only +L rooms to be filtered and allows network operators to set a room +L..

Example:

/as filter channel ircop

This gives the power to filter rooms to a fairly large number of people, but still only to those who are specifically trusted by the network.

Usage: FILTER CHANNEL LOCAL <setting> [option]

This controls how messages to the room from local users are dealt with. WARN can be set on or off. You can set one of the other three options. WARN controls what the sender sees while the other options control what the recipient sees.

CENSOR - Replace the offending text with asterisks

DROP - Block the entire message

NONE - Perform no profanity filtering

WARN - Send a warning to the sender

Examples:

/as help filter channel local <topic>

You should generally set warn on unless you have local set to none. Otherwise the sender will not know that the message contained offensive text.

Usage: FILTER CHANNEL LOCAL CENSOR

Replace unacceptable words with asterisks for users in channels on the local server.

Examples:
 
/as filter channel local censor

This command should be used when you want to censor the content of a message. This will only affect the users on the local server and will not affect users that are on remote network servers.

Usage: FILTER CHANNEL LOCAL DROP

Block the entire message from getting to the user in the local channels.

Examples:
 
/as filter channel local drop

Instead of replacing the profane word with asterisks, this will drop the message from getting to other people on the local server.

Usage: FILTER CHANNEL LOCAL NONE

Ignore the profanity in channel messages.

Examples:
 
/as filter channel local none

This should be used to ignore any words sent to a channel that trigger the filter. It allows you to turn it off locally but to filter it globally.

Usage: FILTER CHANNEL LOCAL WARN <on|off>

Send the user a warning about the profanity.

Examples:
 
/as filter channel local warn on

/as filter channel local warn off

This will warn users on the local server that what they have just typed has triggered the profanity filter.

Usage: FILTER CHANNEL NONE

This prevents profanity filtering from happening in any rooms.

Example:

/as filter channel none

This is a good setting if you want your users to be able to say anything they want within rooms.

Usage: FILTER CHANNEL REMOTE <setting> [option]

This controls how messages to the room from remote users are dealt with. WARN can be set on or off. You can set one of the other three options. WARN controls what the sender sees while the other options control what the recipient sees.

CENSOR - Replace the offending text with asterisks

DROP - Block the entire message

NONE - Perform no profanity filtering

WARN - Send a warning to the sender

Examples:

/as help filter channel remote <topic>

You should generally set warn on unless you have remote set to none. Otherwise the sender will not know that the message contained offensive text.

Usage: FILTER CHANNEL REMOTE CENSOR

Replace unacceptable words with asterisks

Examples:
 
/as filter channel remote censor

This command should be used when you want to censor the content of a message. This will only affect the users on remote or networked servers.

Usage: FILTER CHANNEL REMOTE DROP

Block the entire message from getting through

Examples:
 
/as filter channel remote drop

Instead of replacing the profane word with asterisks, this will drop the message from getting to other people in channels on remote servers.

Usage: FILTER CHANNEL REMOTE NONE

Ignore the profanity

Examples:
 
/as filter channel remote none

This should be used to ignore any words to the remote servers that trigger the filter. It allows you to turn it off remotely but to filter it locally.

Usage: FILTER CHANNEL REMOTE <on|off>

Send the user a warning about the profanity

Examples:
 
/as filter channel remote warn

This will warn users on the remote server that what they have just typed has triggered the profanity filter.

This command controls who may set a room to be filtered for profanity. It can be set to ALL, NONE, CHANOP, IRCOP, SA, or ADMIN. If it is set to all then all rooms will be filtered. If it is set to none then no rooms will be filtered. The sa option causes only +L rooms to be filtered and allows services administrators to set a room +L..

Example:

/as filter channel sa

This gives a moderate number of people the ability to filter rooms. But room filtering will probably still be somewhat uncommon. This is good if you want it only to be set occasionally, but to still have a decent number of people able to set it when they think it appropriate.

Usage: FILTER LIST

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.

Usage: FILTER MAP <char> STOP|SELF|ORIG <char>

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.

Usage: FILTER MAP <char> ORIG <char>

Causes the character to restore its original (default) mapping

Example:

/as filter map '3' orig

Usage: FILTER MAP <char> STOP|SELF|ORIG <char>

This will set the target character as itself. 

Example:

/as filter map '3' self

Sometimes you'll have set a certain character to map to another, or act as a stop character. If you just want it to map back to itself and not use our defaults or settings that you previously had then use this command.

Usage: FILTER MAP <char> STOP <char>

Create a stop character

Example:

/as filter map '3' stop

Stop characters allow you to search for profanity inside of another string. The text being sent is separated into works along the stops. The space character is always a stop. Other characters can be configured to be stops or not. 
If someone was advertising a URL and you wanted to search for both www.foo.com and http://www.foo.com you could map / as a stop and www.foo.com would be seen as the filtered word.

Usage: FILTER MESSAGE <setting>

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.

Usage: FILTER MESSAGE ALL

This will cause all private messages to be filtered for profanity regardless of +L setting. This works with the FILTER MESSAGE LOCAL and FILTER MESSAGE REMOTE options.

Example:

/as filter message all

This will create a server where people are less likely to use words you object to privately. This may be a good idea if your server strongly wishes to discourage the use of certain terms.

Usage: FILTER MESSAGE LOCAL <setting>

This sets how messages containing profanity from local users will be dealt with. You can set one of the following three options: CENSOR, DROP, NONE. In addition, WARN can be set on or off. The first set controls what the recipient sees and WARN controls what the sender sees.

CENSOR - Replace unacceptable words with asterisks

DROP - Block the entire message from getting through

NONE - Ignore the profanity

WARN - Send the user a warning about the profanity

Examples:

/as help filter message local <topic>

This will only be effective if FILTER MESSAGE is set to ALL or SOME. If it is set to SOME then it will only apply to +L users.

Usage: FILTER MESSAGE LOCAL CENSOR

Replace unacceptable words with asterisks

Examples:
 
/as filter message local censor

This command should be used when you want to censor the message. This will only effect the local server and will not effect what servers that maybe connected to you see.

Usage: FILTER MESSAGE LOCAL <setting>

Block the entire message from getting through

Examples:
 
/as filter message local drop

Instead of replacing the profane word with asterisks, this will drop the message from getting to other people on the local server.

Usage: FILTER MESSAGE LOCAL <setting>

Ignore the profanity

Examples:
 
/as filter message local none

This should be used to ignore any words that trigger the filter. It allows you to turn it off locally but to filter it globally.

Usage: FILTER MESSAGE LOCAL <on|off>

Send the user a warning about the profanity

Examples:
 
/as filter message local warn on

/as filter message local warn off

This will warn users on the local server that what they have just typed has triggered the profanity filter.

Usage: FILTER MESSAGE NONE

This will override LOCAL and REMOTE profanity settings to turn off all profanity filtering for private messages.

Example:

/as filter message none

This creates a server where people are allowed to say anything they wish in private messages.

Usage: FILTER MESSAGE REMOTE <setting>

This controls how messages containing profanity from users on other servers are dealt with. This works the same way as FILTER MESSAGE LOCAL.

CENSOR - Replace unacceptable words with asterisks

DROP - Block the entire message from getting through

NONE - Ignore the profanity

WARN - Send the user a warning about the profanity

Examples:

/as help filter message remote <topic>

See FILTER MESSAGE LOCAL for more information.

Usage: FILTER MESSAGE REMOTE CENSOR

Replace unacceptable words with asterisks

Examples:
 
/as filter message remote censor

This command should be used when you want to censor the message. This will only effect the local server and will not effect what servers that maybe connected to you see.

Usage: FILTER MESSAGE REMOTE DROP

Block the entire message from getting through

Examples:
 
/as filter message remote drop

Instead of replacing the profane word with asterisks, this will drop the message from getting to other people on the local server.

Usage: FILTER MESSAGE REMOTE NONE

Ignore the profanity

Examples:
 
/as filter message remote none

This should be used to ignore any words that trigger the filter. It allows you to turn it off remotely but to filter it locally.

Usage: FILTER MESSAGE REMOTE <on|off>

Send the user a warning about the profanity

Examples:
 
/as filter message remote warn on

/as filter message remote warn off

This will warn users on the remote server that what they have just typed has triggered the profanity filter.

Usage: FILTER MESSAGE SOME

This will cause filtering of private messages to apply only to +L users. How profanity is dealt with is then specified by FILTER MESSAGE LOCAL and FILTER MESSAGE REMOTE.

Example:

/as filter message some

This allows users to choose whether they want to have messages sent to them to be filtered.

Usage: FILTER WORD [<command>] [<word>]

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.

Usage: FILTER WORD ADD [<word>]

This will add prohibited words to your server.

Example:

/as filter word add satan

The exact strings will be filtered and any text that matches them when mappings are taken into consideration. See FILTER MAP. You cannot add wildcards into the profanity filter.

Usage: FILTER WORD DEL [<word>]

Removes a specific filtered word.

Example:

/as filter word del satan

To get a complete list of words that are currently configured to be filtered see the FILTER WORD LIST command.

Usage: FILTER WORD LIST

Lists the entire filtered word list on the server.

Example:

/as filter word list