Welcome to the NewNet IRC Network Channel Operator Class.
This class will cover the basics of channel operation/management, floods, and user@host masking. This is the place to learn basic IRC channel commands to help manage your channel.

This class is brought to you by #services, and all those that have helped make it what it is. Many servers have their own Admin/IRCop/help channel. A list of server Admin/IRCop channels can be found at the end of this class.
--===========================================================================--
All comments/suggestions about this class should be sent via e-mail to LadyBear@ladybear.com. Thanks!

This class will not cover the Channel Services bot (ChanServ and NickServ) commands or IrcOp commands. Those classes are available in #services-help.

When you see a word(s) separated by a |; it usually means or. DOS wildcards are used with many commands; a * is used to replace multiple characters and ? is used to replace a single character. A - means take away and + means to give.
--===========================================================================--
Section 1: Channel Modes

While being a channel operator, you have at your disposal, several channel modes to better enable you to manage the channel. These modes each have a unique function, while some are used more often than others.

The list of available commands at your disposal as a channel op are: +n, +t, +m, +s, +p, +i, +l, +k

+n = no outside messages - Syntax : /mode #chan +n
While IRC'ing, users have the ability of /ping'ing or /notice'ing a channel. This can easily be abused and turn into flooding. To help prevent that from happening, the +n mode forces all users to be *inside* the channel before they can /notice or /ping it.

This is a widely used channel mode; its highly recommended to use it.

+t = only ops set topics - Syntax : /mode #chan +t
Another good mode to set in your channel. This allows only channel operators to change the topic. It prevents non ops from changing it to obscene or undesirable topics.

+m = moderated channel - Syntax : /mode #chan +m
In a +m (moderated) channel, only channel operators and users with +v (voice) set may speak. Everyone else receives an annoying Cannot Send To Channel error.

** Note : This mode is very useful for regaining control of a chaotic channel, although it has little other practical use. (see +v later on)

+s = secret channel - Syntax : /mode #chan +s
A +s channel does not show up in a /list of channels, and it's name will not show up in the /whois of people in it, either.

+p = private channel - Syntax : /mode #chan +p
A +p channel will, like +s, not show up in a channel /list, but it *will* show up in the /whois of it's occupants.

+i = channel invite-only - Syntax : /mode #chan +i
A +i channel requires an invitation in order to enter. Everyone who tries to enter without an invitation is sent a Cannot join channel (+i) - Channel is invite-only message. (see +L next)

To invite someone to the channel, you type /invite [nick] #channel or /invite [nick]. Once invited any user may invite others to join the channel.

+L = Channel Limit - Syntax : /mode #chan +l [max # of users]
A +L channel only allows a certain number of users to be in it at any given time. The limit must be raised to /invite when the user limit has been reached. ** Note only a channel op may raise the limit.

+k = Channel Key Required - Syntax : /mode #chan +k [key word|phrase|number]
And finally, +k channels require a password in order to enter. Those who don't know the password are sent this message:
Cannot join channel (+k) - [Channel key required]

** NOTE ** When /invite'ing a user to a +k channel you need to send them the password in a separate /message.

** Note that all these command can be prefixed with - to disable that function

--===========================================================================--
Section 2: User Modes

When you are serving as a channel operator, there are three user modes you may apply to others. These are +v, +b, and +o.

Two of these can be used to help manage your channel when things get out of hand (+v & +b).

+v = voice - Syntax : /mode #chan +v [nick]
A user with +v set may speak in a moderated channel. This is normally used with +m (moderated); mentioned in the section above. You will see a + next to a nick in your nick list. This means they have voice or speak status in a(n) (un)moderated channel.

This is most useful when you have too many people talking at once. You would first set the channel +m (/mode #chan +m) and then certain users (maybe) to +v (/mode #chan +v nick).

+b = banned - Syntax : /mode #chan +b [nick|u@h|host mask]
** NOTE ** u@h and host mask will be covered later.

A user with +b set on a channel may not enter. They will get Cannot join channel (+b) [You have been banned]. This may also be set on a user while they are in the channel. It usually gives them a strong indication to cease and desist because if they are kicked they won't be allowed back for a while. (see /kick below)

** NOTE ** A user with +b set in a channel is not able to talk, /notice #chan, or /ping #chan if they are not an op (+o) or voiced (+v)

+o = channel operator - Syntax : /mode #chan +o [nick]
Be very careful with who you give this to. Channel operators may change channel modes, change the topic, kick, and deop people or possibly takeover a channel. Persons with an @ next to their nick in your nick list are channel operators.

--===========================================================================--
Section 3: Kicks and Bans

During the course of being a ChanOp, it may become necessary to manage your channel in a more severe method or find it best to request the user to stop their misbehaving. If they do not stop after a few requests then a /kick is in order as a warning.

Syntax : /kick #chan [nick] [reason]
The portion of the command is needed by most irc software and will be displayed to the person being kicked in similar fashion to:
*** GoBoom has kicked you from #chanop (for abuse of any nature)
** NOTE ** Please give a valid reason.

Should they continue their abuse after a couple of kicks then a /ban or +b is in order for a stronger warning.
Syntax : /mode #chan +/-b [nick|u@h|host mask]
Finally if they refuse to stop you can kick them one final time after the /ban or +b is set and they shouldn't come back.

When a user is determined after repeated kicks|bans to continue their abuse a combined /mode +b and /kick (reason) is justified on immediate joining of your channel or if your IRC software has permanent banlist capabilities then just add them to that list and it becomes automatic everytime you logon to IRC for your channel.

** NOTE ** When banning someone, it is best to use *!*user@host or *!*@exact address. If a nick is used, all the person has to do is change nicks to get around it.

--===========================================================================--
Section 4: Floods and Flood Avoidance

Although the IRCops do their best to catch them, there will always be some individuals who get their fun by making the IRC experience of others utterly miserable.

These individuals are known as flooders. There are 4 types of floods that can make life more difficult for you.
1.) Text Flood
2.) CTCP Flood
3.) DCC Flood
4.) ICMP Bomb

** NOTE ** All floods are variations of these.

I will not go into descriptions of these. Suffice it to say that the best way to take care of most floods is:
To /ignore [nick] [type] **Note** : Some clients allow you to specify the type of /ignore or allow you to turn DCC/MSGS/CTCP off. Check your help files. OR /silence +|-[u@h|host mask].

Ignore is used from your client, uses the persons nick, and may allow flags; as mentioned before.
Silence is used from the server and doesn't allow flags or nicks. It uses u@h or host mask (usually). * Note * This server allows use of a nick also, but if they change their nick, they can get around it. Also, it is server dependent. It may not work on other networks. Silence blocks all /msg's, /notice's, /dcc's. It does not block channel text.

** NOTE ** You should turn off auto-accept dcc sends and do not accept files from people you don't know.
To protect against ICMP attacks, get the nuke fixes from http://www.ladybear.com/services just follow the exploit link.

It is best to log such acts and notify an IRCop. They may ask to see your log. (/DCC these; do not post in channel) It is not the responsibility of IRCops to stop or prevent flooding. The ONLY time they will/should get involved is when it is a danger to the net or their server.

AGAIN; Your best defense is to /ignore or /silence the troublesome user. Also, you can change your nick to thwart most floods.

--===========================================================================--
Section 5: Masks & Wildcards

A wildcard is used the same way it is in DOS. An asterisks (*) is used for many characters and a question mark (?) is used for a single character. User@Hosts or user@ip are shown when a person does a /whois on users. Masks are variations of these using wildcard characters. Several of the commands we talked about earlier use u@h masks or host masks.

As an example say we do a /whois johndoe. What may be shown as his user@host address will be shown 1 of 4 different ways:
1.) johndoe@nw1-2.nowhere.com
2.) ~johndoe@nw1-2.nowhere.com
3.) johndoe@103.102.55.6
4.) ~johndoe@103.102.55.6

A MASK may be made from anyone of these. You will notice that tilde (~) is in front of two of the addresses. The tilde indicates that the person is not using an ident daemon (identd).

In almost all cases an * should be the first and only character before the name johndoe@. This eliminates the tilde so that command(s) using a mask won't miss the user should they use identd.

User MASKs are in the form (using the example) :
1.) *!*johndoe@*.nowhere.com
2.) *!*johndoe@103.102.55.*
3.) *!*johndoe@103.102.* (in some rare cases)
A ? may be used anywhere within the mask to replace a particular character if you choose.

These are the types of MASKs you need to use with most commands like /ban /kick /silence and /ignore that have the ability to use them.

Host MASKs are usually in the form (using the example) :
1.) *!*@*.nowhwere.com
2.) *!*@103.102.55.*
3.) *!*@103.102.* (in some rare cases)
NOTE: If this type of MASK is used you may end up /ban'ing (sometimes called a site ban), /kick'ing or /ignore'ing whole domains/sites and maybe some of your (possible|future) IRC friends.