First, let's define some terms that will be used throughout this document:

1) Undernet -- This is the IRC server network you have connected to and which this document concerns. It is not to be confused with the Internet, which is the name for the whole worldwide physical network upon which all the various services such as e-mail, the Web, Usenet news, IRC and other computer data travels.

2) Server -- The IRC server that you have connected to, or any other server in the Undernet.
If you are not sure of what server to connect to or need a more detailed explanation of a specific server.
A list of servers can be found at http//www.undernet.org/servers.php

3) Client -- Clients connect to servers (i.e., servers serve clients the same way a waiter serves restaurant patrons). Your client is your IRC program or browser application that allows you tpo connect to and to chat on IRC.

             Index of sections:

Go to Top

Where < parameters > is a space or comma separated list of one or more of:

		< max_users	Show all channels with less then max_users.
		> min_users	Show all channels with more then min_users.
		C < max_minutes	Channels that exist less then max_minutes.
		C > min_minutes	Channels that exist more then min_minutes.
		T < max_minutes	Channels with a topic last set less then max_minutes ago.
		T > min_minutes	Channels with a topic last set more then min_minutes ago.

For example: /list <3, >1, C <10 lists channels with less than three users and more than one (i.e., two) and which are less than 10 minutes old. A simpler example (and more typical of the way people use it) is /list >10, to list channels with more than 10 people.
Your IRC client may also have a command to streamline the channel list process, and may also allow searches by topic or key word (Mirc has such a channel search feature). The /list command does not list secret or private channels (see section 3 for more information on this).
Using /list with a specific channel name such as /list #userguide will return a more specific set of channel names therefore bypassing the number of people in any said channel.

In mIRC you can also use /list *keyword* This will list all channels with "keyword" in their names or topics.
Check your IRC program for their search feature.

You may have tried to connect to a server and received a "No more connections" message. This server message means that the server is full (has reached its maximum allowed connections) and cannot complete any more connections until other clients quit their IRC session. This is one of the reasons that more than one client connection is not allowed on many servers.

Some people use clones to flood people (then called floodbots) in an attempt to cause people to loose their connection to IRC. Flooding other people off of IRC is not only an immature thing to do, is in fact a crime, often called DoS or Denial of Service, in most countries. Flooding also wastes bandwidth which contributes to lag.

Clones generally get disconnected and banned, and persistent clones from the same host will be banned from all Undernet servers (G-lined). Additionally, the ISP of the clones will be contacted and asked to take action against the abusive users. This can lead to suspension of, or removal of, the offender's account as well as reporting them to law enforcement agencies. For more information on K-lines and/or G-lines, see the K/G-line section below.

*Note* If you want to know the policy of the server you are connected to, type /motd in your status window. By connecting to an Undernet server, you are agreeing to the info listed in that server's MOTD (Message Of The Day).

You can also op more than one person at a time:

By the way, you should be careful in choosing who you op - don't op just anyone, but also make sure the channel has enough ops in case some are disconnected suddenly (for whatever reason), since the channel may be left opless. If you op someone and they deop all the other ops, then the channel has not been taken over, since they got ops legitimately.

In this case, there is nothing you can do, so don't ask an IRCop for help. Instead, learn to be cautious in who you op, and never op someone just because their nick is that of your friend. Get into the habit of remembering and recognising people by their addresses rather than their nicks or any other way you work out so that you can positively identify people you trust.

+n  This mode means no external messages to the channel, i.e., you can't send a /msg to the channel without being inside it. For example, if #popsicle is +n and cArLiLLoS, who's not in #popsicle, tries to send a message using /msg #popsicle boo! scared ya!, he will get a message similar to

+t  This mode means only ops can set or change the topic for the channel, using /topic #channel <topic>. If the channel is -t, then anyone can change the topic, e.g., /topic #popsicle This is the place for smurfs to chat and flirt!

+p  Channel is private. When a /WHOIS is performed from outside on anyone in a private channel, the channel will not be displayed in the /WHOIS result. It won't be shown in a channel listing either. Suppose banjo is in channels #userguide and also in #smurflove (which is a private channel). If stoney` (who is not in #smurflove) does /whois on Banjo, this will be the output

However, smurfette, who is in #smurflove with Banjo (*grin*), will see the following channels listed instead because she is also in the private channel:

In a secret channel, this is not possible, since doing a /who #channel does not reveal who is inside. Note that even with a private (+p) channel, any people inside who are +i (invisible) will not show up in a /who #channel listing. If you attempt to do a /who on a secret channel, the server will not protest, but will merely send you an empty listing.

+m  This is a moderated channel, which means only ops can talk. Non-ops will get the response:

+v  This is for voice mode; it lets the person speak if the channel is moderated, even if they are not ops. Obviously a channel op need not be +v since they can already speak (but it's possible to set +v on an op anyway). If #popsicle is moderated (+m) then Banjo (who must be an op) can let greysmurf talk by either making him an op or by /mode #popsicle +v greysmurf. Someone with voice in a channel has a + before their nick, similar to the way an op has an @ before their nick.
Some channels that are not moderated use the voice setting to show who in the channel is a helper or a channel op who chooses not to be oped at the time. A channel does not have to be moderated (+m) to "voice" people and thus have a + in front of their nick.

+i  This means the channel is invite-only, meaning you must explicitly be invited by an op of the channel, using /invite (nick) #channel before you can join the channel. If you are not invited, you will be unable to join the channel. So if #popsicle was +i and Banjo (an op) wanted to let darksmurf join the channel, he should /invite darksmurf #popsicle. Otherwise darksmurf would get the following message if he tried to join:

Any "overlapping" bans will be removed by the server first. For example, if you had banned *!*john@*.abc.com and *!*jane@*.xyz.com, then if you ban *!*@*.com, those 2 bans will be removed, since the *!*@*.com ban covers them, making them redundant.

Modes can be set on and off in one /mode command, and may be combined at will, e.g., /mode #popsicle +mno-t+sl stoney` 10. This would set the channel moderated, no external messages, op stoney`, anyone can change topic, make it secret and limit the channel to 10 people. You can see this by looking at the order of the modes given and the order of the arguments specified. The first mode from the left which requires an argument will use the first argument, the second will use the second and so on. Don't worry if you don't understand all this yet. It will come with time, and you can ask other people on IRC too.

+r  Now available as a channel mode, sets the channel as restricted to registered users only. If the channel is set +r then a user who is not registered with CService, with a legitimate username, valid email address, and logged into X at the time, cannot enter the channel until +r is taken off ( set -r). This is used to restrict flooders and clones from the channel and allows only registered users to join.
This mode is set the same way any other mode is for a channel.../mode #Tidbits +r. This mode is for all channels, not just for registered channels (with @X).

Note: Most IRC clients (programs) automate many channel op functions. Consult your program's help files.

Go to Top

X is the Undernet Channel Service Comitee's (called CServiuce or CSC) bot. It is provided for established channels to provide channel stability. An established channel is one that has been running for some time and has enough channel traffic to need X. (For info about CService and X join #cservice or visit http://cservice.undernet.org
A registered channel is one that has been registered with the Undernet Channel Service, and has thus been granted the use of the channel service bot X.

What does X do? X will keep your channel open for you by always being opped, even if no one is in the channel thus preventing channel takeovers. X is also used to maintain all channel modes set (so the channel doesn't lose the banlist, topic etc.), X also maintains a userlist of those who are channel ops. X also provides channel security because they enable you to always retake your channel if it gets taken over. X has the distinct advantage of being impossible to kick or deop by users not in it's user list), which makes it, and a channel with it, very secure indeed.

Before registering a channel, you need to have a registered username.
A username is how you are recognized by X in order to get ops in registered channels or apply to register or support the registration of a channel. A username doesn't need to be the same as your nickname and it doesn't mean you are registering your nickname (you can't register a nickname). Having a username will give you the ability to set yourself +x (host hiding) as explained in section 3.1
Note Host hiding protects you from denial of service attacks (DoS or nukes as they're sometimes called) as it will be impossible for anyone to find out you real user@host or IP address.
To register a username, you need to go to http://cservice.undernet.org/live . Click on "Register!" and CAREFULLY follow the instructions. You will have to supply a valid email address to register. Use your ISP email address where possible. Free email addresses are not allowed as they enable one person to register more than one username, which isn't allowed.

You can register a channel at the cservice site at http://cservice.undernet.org/live. Just follow the instructions. It is a simple process. Just understand that you have to be patient. It takes awhile for the registration process to go through or be denied in either case.
You can read the Channel registration policy at http://cservice.undernet.org/live/regproc/aup.php.
Note that CService registers established channels only; the registration process is not for creating channels.
You will need 10 supporters for your registration application who are regular visitors of the channel who have already registered their usernames. For more information, ask in #cservice, or #userguide, or read about cservice at http://cservice.undernet.org.

If you just want to create a channel, type /join #channelname. If the channel currently exists, you will join it. If it doesn't, it will be created, and you will automatically be a channel operator for that channel. So if smurfette wants to create a channel called #beautyparlour, she can just /join #beautyparlour.

Note again, that if that channel is not registered or claimed by someone else you will be the sole operator in that channel. And then you would need to establish the channel (before trying to register it) by having your friends and supporters join and maintain the channel until it has enough traffic to qualify for the X channel bot.
Note also that Undernet does not support spamming of channels in any way and retribution, in the form of G-lines or being put on the "no registering channels list" if you spam in other channels to advertise yours.

If you have more questions or would like more information on channel registration, drop into #cservice or #userguide and ask.

If you are wondering if someone is an official CSC (channel service committee) personnel, then typing /msg X verify <nickname> will result in one of the following responses:

If they are a CService admin:

IMPORTANT!!! NEVER give your password to anyone claiming to be an IRCop or CSC representative, as the real ones will never ask you for it. If you think someone is impersonating a cservice official, you can report the user to #cservice. If someone is impersonating an IRCop, report them to #zt or any IRCop.

If someone is an IRC operator, their /whois information will show them to be one:

IRC ops are responsible for keeping the network running smoothly and maintaining the servers. IRCops are under no obligation to help opless channels or channels which have been taken over. While many IRCops do help users, they are not required to do so. Many IRCops work behind the scenes, maintaining the network, getting rid of floodnets, clones and abusive users, and taking care of the server they are responsible for and don't always have time to help users.

For more information about IRCops and what they do, see the oper FAQ on the documents project website.

CService Admins. and helpers are responsible for channel registration, X, usernames and #cservice. While the channel service committee (often called CSC or cservice) has nothing to do with running the servers or maintaining the network. There are some people who are both cservice personal and IRCops. Cservice works closely with IRCops in making sure that abusive users are removed from the network.

If you think you need to speak with an IRCop, join #ZT and explain the reason you need to speak with one. You must be patient when asking for help as the #ZT personal are usually busy helping others in private and no one is ignoring you. Never /msg anyone in #ZT, state your problem in the channel then wait for someone to help you.

If you want to know what X commands are available to you, type /msg X showcommands.
If you don't know how to use a command, type /msg X help <commandName>.
For example if you needed help on the adduser command, you would type /msg X help adduser to get X's online help.

All users who are channel ops on registered channels are encouraged to read the X commands.txt file. You can download the X commands.txt from CService Documents and Forms section.

If you're not sure whether X is actually capable of doing what you want to do with it, ask in #cservice or #userguide. As you should have guessed by now, #cservice is the channel for X help and information on channel and username registration.
When asking questions in #cservice, please give the channel name, and tell if you have X or not and what access level you have so that you can be better helped.

Note that #cservice is NOT for general bot help or bot questions; it only deals with X, channel registration, usernames, and related topics. It is not for general help with IRC , #userguide is for that.
The volunteers in #userguide will be able to answer all your questions and/or direct you to where you can get the proper help you need.

Please remember that help channels can get very busy and the volunteers may be helping several people via private message, so be patient. Never message anyone in a help channel unless you are asked to do so. The best thing to do is state your problem or question and wait for someone to help you. If you are not helped after 5 minutes, then repeat you question or problem.

Go to Top

The answer to this depends on what kind of help you want.
If you are new to IRC, then #userguide would be a good place to start with your questions. If you don't get the answers you need there, you will be directed to the proper channel or website.

There are many channels that deal with specific topics and their channel name will often be that topic. For example if you are looking for help with a program (such as your IRC client), try joining that channel. If you use theBestChat (not a real IRC client) for IRC, you may try joining #thebestchat channel. If that channel exists, your search may be over.

As a general guide, if you have a problem with X, a registered channel, or usernames then ask in #cservice. If you want to report abusive users or need help in a channel, then #ZT is the channel to join. If you have any other problems or questions, join a general help channel such as #userguide.

Go to Top

You can get an up to date list of servers along with their port connects, Admins, IRCops and server information at http://www.undernet.org/servers.php.

The best way to find out is to read the server's message of the day (MOTD), which many clients automatically display when you connect to the server.
Typing /motd will display the MOTD of the server you are connected to.
It will usually display the server's bot policy and other information.

Go to Top

If someone is harassing you, get their address and /ignore it.

If Banjo wanted to ignore stoney`, then banjo would first get stoney`'s user@host by doing a /whois stoney`.
Suppose stoney` is stoney`@slip34.mushouse.com.Then Banjo could type /ignore *!*stoney`@*.mushouse.com

Now suppose stoney` is using Undernet's host hiding feature, stoney` is troublemaker@stoney.users.undernet.org. Typing /ignore *!*@stoney.users.undernet.org will ignore everyone who's username is stoney.
Since only one person can have the username stoney, only he will be ignored.

Many IRC programs have ways to streamline the ignore process and set wildcards (the *) for you. Consult your IRC client's help files.

Remember, /ignore is a powerful and effective tool. When you ignore someone, you don't see what they say on channels you're in, you don't see any messages or notices from them, you don't receive DCC send or chat requests, and you won't get CTCP (pings, versions, etc.) from them either. In short, they are basically GONE from IRC from your point of view.

The ignore command is an IRC client command not a server command. Your IRC client/s help files will show you how to set and remove /ignore.

This is the method of choice for dealing with people who harass you or annoy you excessively, and much better than asking someone else to do something about it for you.

Nothing. Absolutely nothing. The fact is that it isn't your nick. There is no nick ownership on the Undernet. If you want, you can try asking the person using it to let you have it, but they are under no obligation to do so. If they refuse to give it up, then that is tough luck. Your IRC friends should learn to recognise you by your address (or username if you choose to register one) or via personal information only you would know rather than your nick for this reason.

If this is not feasible because there are many people or because you have bots in the channel, then go to #ZT, and ask politely (without shouting) for an IRCop to op you or someone else in your channel, then wait patiently for someone to help you. Note that the whole channel must agree on someone to be opped, otherwise no-one will be opped and the channel will be left to stay opless.

If there is some form of proof that someone is usually an op on the channel, be prepared to show that proof as well as an explanation how the channel lost ops.

Remember, IRCops are under no obligation to op anyone on any channel.

Go to Top

IRC Operators are chosen for their abilities at running servers, routing the network, knowledge of IRCu, and trustworthiness. There is no form, mailing list, or person to ask, and there is no list of future operators.

Normally, the way one becomes an operator is to be chosen by a server administrator, and display a working knowledge of IRCu, routing issues, and various other "behind the scenes" aspects of an operator's "life".
The /kills, channel mode changes, etc. that are visible to users are a small part of the many duties of an IRCop.

For information on just what an IRC operator does, just click here. This is an extremely helpful document that outlines all the various duties which an IRC operator performs on a day-to-day basis.

As of this writing, the minimum requirements for linking a server to Undernet is a dedicated machine running 24 hours, 7 days a week and a MINIMUM of MULTIPLE E1/T1 to SEPARATE providers. Single-homed 10mbps or higher speeds may apply, however multiple T-3/OC-3/DS-3 connections are preferred.
You must be running the latest Undernet IRCd (no windows machines allowed).
If you would like the latest information, as well as instructions for applying for a test link to Undernet, please go to the following web page http://www.routing-com.undernet.org

All the mailing lists, listed below are to help you, the user if answer various questions about all aspects of Undernet. The volunteers are trained to answer inquiries from newbies, people who are new to IRC asking the basic questions or having basic problems related to IRC to the most experienced IRC user.

Most Undernet committees have their own mailing lists for their members to use. If you want to help out, and you are thinking about joining an Undernet committee, you can find a complete list of contact addresses on the main Undernet site http://www.undernet.org, by clicking on committees.

Not all Undernet committees are open lists, or lists that anyone can join. To find out if a committee allows users to subscribe to their lists, email the committee/s and ask about their policies.

The following is a list of addresses users can email as well as the list's functions

		user-com@undernet.org	The Undernet User Committee, the voice for users on the Undernet. For Undernet related matters and for user suggestions.
		promotions@undernet.org	For promoting the Undernet to current and potential users.
		abuse@undernet.org	For reporting violations of Undernet's AUP (see Acceptable Use Policy on the documents website), complaints about IRCops, and G and K-line problems.
		documents@undernet.org	For discussion of, and the updating of, official Undernet documents and FAQs. You are welcome to email this list with suggestions about new documents you would like to see and/or suggestions on how to improve a current document.
		help@undernet.org	For general IRC help.
		cservice@undernet.org	For general channel service questions.
		X@undernet.org	For For channel registration and username related problems or questions.
		coder-com@undernet.org	For discussion of Undernet server coding.
		routing-com@undernet.org	For new Undernet server applications.

The Volunteers on #userguide, the Undernet User Committee user help channel, will me happy to answer your questions and/or direct you to the proper place. #userguide is also a great place to discuss ways to make Undernet better. The channel is a great place to have your voice heard, so feel free to join the channel anytime.

Help is easy to find if you are patient and direct with your questions. Please refrain from emailing several lists at a time with the same question. If one list can't help you, or thinks you would be better helped by another committee, they will refer you to the proper people or list or just forward your email to the proper list. And again, be patient, as all the email lists are manned by volunteers who may have to read and reply to hundreds of emails daily.

Go to Top

Your IRC client's help files can be a good source of general IRC information as well as showing you how to get the most out of your IRC program.


The documents project site has a wealth of information, and the various help channels are manned by knowledgable people who will do their best to assist you. If you have any suggestions for new documents or FAQs, you are encouraged to email documents@undernet.org with your suggestions.

Go to Top

© 1997-2003 Undernet User Committee FV04
This page was last updated September 2nd, 2003
Return to main Documents Project page