Server Commands/SHUN
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | + | '''Syntax:''' <code>SHUN [[!][+|-][$<type>]<mask> [[<target>] <expiration> :<reason>]]</code> | |
| - | + | ||
| - | + | ||
| - | + | Shuns prevent users who match them from sending messages to the server, other than PING/PONG responses. They will not be notified they have been shunned. | |
| - | < | + | |
| Line 14: | Line 13: | ||
'''<mask>''' - This may take two forms depending on the type of Shun being placed; user@host for hostnames, and *phrase* for gcos. If not given, or if its not prefixed by "+" or "-", a list of Shuns will be returned. If the "+" or "-" prefixes are used, then the <expiration> and <reason> parameters must also be given, even if the Shun already exists. | '''<mask>''' - This may take two forms depending on the type of Shun being placed; user@host for hostnames, and *phrase* for gcos. If not given, or if its not prefixed by "+" or "-", a list of Shuns will be returned. If the "+" or "-" prefixes are used, then the <expiration> and <reason> parameters must also be given, even if the Shun already exists. | ||
| - | '''<target>''' - specifies what server(s) the Shun is to be activated/deactivated on. It may be either a server name or * for global. This is rarely used on DareNET due to the fact that | + | '''<target>''' - specifies what server(s) the Shun is to be activated/deactivated on. It may be either a server name or * for global. This is rarely used on DareNET due to the fact that O must be used to place global Shuns. |
'''<expiration>''' - The expiration can be specified either in seconds or as a formatted time (e.g. 2d5m3s). | '''<expiration>''' - The expiration can be specified either in seconds or as a formatted time (e.g. 2d5m3s). | ||
| Line 20: | Line 19: | ||
'''<reason>''' - The reason specifies why the user is being Shunned. It will be broadcasted to all IRC operators who have the appropriate SNOMASK. | '''<reason>''' - The reason specifies why the user is being Shunned. It will be broadcasted to all IRC operators who have the appropriate SNOMASK. | ||
| - | If the Shun currently exists, a prefix of "+" will cause an inactive Shun to be activated, whereas a prefix of "-" will cause an active Shun to be deactivated. If an attempt is made to modify a Shun set by a U-lined service, such as | + | If the Shun currently exists, a prefix of "+" will cause an inactive Shun to be activated, whereas a prefix of "-" will cause an active Shun to be deactivated. If an attempt is made to modify a Shun set by a U-lined service, such as O, the change will be forced to be local. |
[[Server Commands|(Return to Main listing of Server Commands)]] | [[Server Commands|(Return to Main listing of Server Commands)]] | ||
Current revision as of 02:29, 12 October 2012
Syntax: SHUN [[!][+|-][$<type>]<mask> [[<target>] <expiration> :<reason>]]
Shuns prevent users who match them from sending messages to the server, other than PING/PONG responses. They will not be notified they have been shunned.
! - The "!" prefix is used to forcefully place Shuns that would otherwise be denied by the server for being "too wide" (e.g. affect too many users). The ability to use this prefix has been disabled on DareNET.
[+|-] - Optional. Specifies whether the Shun is to be activated or deactivated.
<$type> - The type argument can be used to Shun users whose realname (gcos) matches by using $R.
<mask> - This may take two forms depending on the type of Shun being placed; user@host for hostnames, and *phrase* for gcos. If not given, or if its not prefixed by "+" or "-", a list of Shuns will be returned. If the "+" or "-" prefixes are used, then the <expiration> and <reason> parameters must also be given, even if the Shun already exists.
<target> - specifies what server(s) the Shun is to be activated/deactivated on. It may be either a server name or * for global. This is rarely used on DareNET due to the fact that O must be used to place global Shuns.
<expiration> - The expiration can be specified either in seconds or as a formatted time (e.g. 2d5m3s).
<reason> - The reason specifies why the user is being Shunned. It will be broadcasted to all IRC operators who have the appropriate SNOMASK.
If the Shun currently exists, a prefix of "+" will cause an inactive Shun to be activated, whereas a prefix of "-" will cause an active Shun to be deactivated. If an attempt is made to modify a Shun set by a U-lined service, such as O, the change will be forced to be local.
