There are many modes that can be used on each channel on the AfterNET IRC network that can help you protect as well as control the channel you are in, whether you choose to use services or not.
Modes can be set on your channel using the /mode command. Use can depend on your software, but usually something like: /mode #channel +modes -modes will do. If you have X3, you can make x3 enforce modes by setting them as + or - in the 'modes' setting. For example:
.set MODES +ntCS-ik
will preserve modes n, t, C and S, but not allow modes i and k. Depending on access level in x3, users may be able to override these ‐ configure that via '.set enfmodes'.
The following are channel modes, along with their explanations, that can be used on the AfterNET IRC network to assist you in running your channel. (NOTE: All modes require operator (@) status in the channel to work):
This mode is used to prevent a user matching the mask that has been banned from joining the channel. There are three effective ban masks that wildcard different portions of the nick's full address:
*!*@host.domain *!*@12.34.56.78
This bans the person until they re-dial in to their ISP (thus changing their host). If they have a static IP address, it bans them until the ban is lifted. This is generally sufficient to make them stop their behavior. (In a way, it's almost like a self-imposed G-line in your channel)
*!*userid@*.domain *!*userid@12.34.56.*
This bans just that one person from that ISP. Dialing in again won't affect this ban, but changing user ids will. Normally, people don't change their userid very often, so this ban is quite effective.
*!*@*.domain *!*@12.34.56.*
This is a site ban; it will ban everyone from that ISP. This is most useful when you have a problem user from a certain ISP (domain) that keeps changing their nick or userid and keeps dialing back in. However, it also bans everyone else from that domain as well.
NOTE: Banning someone by their IP will prevent them from rejoining regardless of the address used; what this means for operators is that if someone is using virtual hosts that all are from the same actual IP, banning their IP will prevent them from entering the channel, regardless of what hostname it resolves to.
There are also Extended Bans which can match based on accounts, marks, realnames, etc.
Setting +c blocks mIRC color codes from your channel. The user will get a message in their status that says they cannot send to channel.
Setting +C blocks CTCP messages, except for /me. The user will get a message in their status that says they cannot send to channel.
Users will not be visible in the userlist until they are opped, voiced, change the topic or speak. A good option for a busy channel.
Exceptions are like a special retinal scan that allows you to join a channel if you match, even if you also match a ban (+b). It uses mask just like +b (above) but instead of keeping that person out, they let them in as an exception.
This is how someone is manually half-opped (without using Services to half-op them). This is the command that puts the % beside someone's nick (in some clients). It gives them the power to change modes and topic on the channel and kick/ban people from the channel BUT halfops cannot kick full ops (+o's)
To hop someone
/mode #chan +h nick
To de-hop someone
/mode #chan -h nick
This mode makes the channel reject joins. In order for someone to join the channel, they have to be invited in by an operator in the channel or services such as X3 (or have the key, see +k below). This mode is normally used for private meetings where you don't want the public involved. An operator (@) in the channel can type /invite nick #channel.
/invite bob #privatechat
This mode puts a key on the channel, which acts like a password ‐ You must know the key to get in. The mode can only be removed or changed by using the current key.
To add or change a key to a channel:
/mode #chan +k key
To remove a key from a channel:
/mode #chan -k key
To join a channel that has a key:
/join #chan key
A channel can have a limit to the number of users that can be in it. This mode requires a parameter to set it and number following it (example: /mode +l 15). Once the limit is reached, no more users will be allowed in the channel until there is fewer users, or they get an invite. If set to 0, our network will automatically change it to 1. This method proves useful in preventing flood bots, but is not suggested for large channels or channels that have user counts that may fluctuate unless you get a bot that keeps it updated. Our services offer a dynamic limit to prevent join flooding, see `set dynlimit` (link todo here)
To limit the number of users in a channel to 30:
/mode #chan +l 30
To remove the limit:
/mode #chan -l
By setting “+L #differentchannelname” any joins to your channel will instead be redirected to #differentchannelname. This is handy if you are changing the name of a channel or shutting a channel down. Users can set UMODE +L to prevent the redirect.
A moderated channel restricts normal users from sending text into the channel. Only the ops (+o) and users that are voiced (+v - see Mode “V” later on in this article for information) can talk in the channel. This has two main uses: silencing flooders in the channel, and creating a lecture-type situation (like a classroom) where the flow of text from the lecturer isn't altered by the users in the channel. If used with +k (key), people who join with the key will automatically get +v so they can talk when they join.
Also, if a channel is moderated, clients are blocked from changing their nicks while in that moderated channel.
A moderated channel restricts normal users who have not authed to AuthServ (or using the /auth command) from sending text into the channel. Only the ops, halfops, voiced users, and registered users (+o/+h/+v or registered) can talk in the channel.
Also, if a channel is moderated, clients are blocked from changing their nicks while in that moderated channel.
This mode prevents text from being sent into the channel from a nick that is not in the channel. In most channels, this is very distracting because you cannot reply to what was said - they are not in the channel to see your reply. Setting this mode is the default for most people
This mode stops the channel from being a target of /notice-es
This is how someone is manually opped (without using Services to op them). This is the command that puts the @ beside someone's nick. It gives them the power to change modes on the channel and kick/ban people from the channel.
VERY IMPORTANT: Be careful who you make an op in your channel, because even if you are the founder, they can still kick and ban you! (unless services are in the channel.) See halfops for a safer alternative.
To op someone
/mode #chan +o nick
To de-op someone
/mode #chan -o nick
Set only by ircops, and allows only them to join a channel.
The channel flag 'p' is used to mark a channel “private”. Similar to secret, this flag conceals the existence of the channel from other users. Private channels show as *private*. Setting this flag removes +s (secret) as they are mutually exclusive.
Removes /part and /quit messages. (You still see the part or quit, just not the message attached to it). This is done because many scripts use these messages to spam and its annoying.
Setting +r makes it so that users who have not used /auth to authenticate to AuthServ cannot join your channel.
The channel flag 's' is used to mark a channel “secret”. Similar to private, this flag conceals the existence of the channel from other users. Secret channels don't show up at all. Setting this flag removes +p (private) as they are mutually exclusive.
This mode is good for avoiding spammers and unwanted users, but does not keep them from entering the channel if they already know it exists.
Similar to +c, only instead of telling the user they cannot send to channel, the color codes are just automatically removed from the messages.
This mode restricts changing the topic to only the channel operators (Services can still over-ride this). Mainly, this is used to keep the topic in line. This mode in addition to +n is generally set by everyone.
This mode stops the channel from being a target of /amsg, a mass-messaging feature of ircu. Use this if you are frequently vulnerable to /amsg spam.
This command allows a normal user in the channel to send text into a moderated (+m or +M) channel. In channels that are not moderated, it is frequently used as a status indicator for that nick. In help channels, for instance, it's used to indicate users who help and are “recognized” as helpers by the staff of the channel, perhaps channel operators in training. In chat channels, it might indicate a favored user. In some channels, it is used to indicate gender.
To voice someone in the channel, type
/mode #chan +v nick
To de- voice someone in the channel, type
/mode #chan -v nick
This mode makes it so that only those connected via SSL can join (without an invite.) Note you must be connected with SSL to change this mode.
In addition to Channel Modes, there are also a useful User Modes that can help you while you are visiting the AfterNET IRC Network. These modes are set by typing
/mode yournick
Some clients support /umode as a shorthand for this. Our supported user modes follow.
This mode makes you invisible on the server. For example, if you do a “/lusers” in the server window, it will say something like “There are 681 users and 330 invisible on 11 servers”. All users that have +i set will show up under the “invisible” users. This mode also allows you to hide from a /WHO or a /NAMES command. However, you can still be found if the user knows your nick, or is in a channel with you.
To set yourself invisible
/mode yournick +i
It is possible to set up a channel such that joins to that channel actually redirect to a different channel.
Having usermode +L set will prevent that, so that you join only the original channel name you asked for.
Setting +R will make it so that people who are not authenticated with AuthServ will not be able to send you messages.
Enabling +w allows you to see communications about the status of the network from IRCOPS.
Enabling +x when you are logged into AuthServ causes your hostname to change to accountname.Users.AfterNet.org, or to another host if you have had one setup (usually in exchange for a contribution)