Undernet IRC Primer

Version 2.01 (last updated: 8/9/97)
Written by loki (Comments/flames/free gifts go to loki@undernet.org).
Additional thanks go to frncheez and to the rest of doco-com.
WWW: http://www.user-com.undernet.org/documents/uprimer.html
FTP: ftp.undernet.org/irc/docs/uprimer.txt

Note: Any use of the word "he" in this FAQ may be freely replaced with "she" and was used purely for convenience.

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 available (e-mail, the Web, Usenet news and IRC) travel.

2) Server -- The IRC server that you have connected to, or any other server in the Undernet.

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.

Index of sections:

 1.......The new /list command, and how to get a list of servers.
 2.......What clones/flooding are, and what k-lines, autobans, etc. are.
 3.......Descriptions of all user and channel modes.
 4.......What a registered channel is, the Undernet Channel Service, X/W and IRC operators.
 5.......Where to find general help on IRC.
 6.......Undernet servers, and their policies on bots.
 7.......What to do if you're being harassed, and other general IRC problems.
 8.......What to do if you want to connect a server to the Undernet.
 9.......A list of mailing lists available for the Undernet and what they are used for.
10......You haven't helped me...where should I look?

Section 1

1.1  How come /list isn't working?

Many Undernet servers have modified the way /list works as replying to /list requests from users was consuming a very large amount of bandwidth. It still works, but may list only channels with at least 15 users, or something similar to that. If /list isn't working, you can try /whois X and /whois W to list registered channels.

Here is the complete syntax:

Usage on ircII: /quote list (parameters)
on mIRC : /raw list (parameters)

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. As it always has, the /list command does not list secret or private channels (see section 3 for more information on these).

Section 2

2.1  What are clones? What is flooding? Why are clones bad?

Simply put, clones are multiple connections from the same host, that is, more than one client/IRC program connected to the Undernet from the same hostname. Why is this bad? Because servers have a limited number of connections they can handle (the number varies between servers depending on the hardware they are running on), and having someone use up more than one connection is a waste.

I'm sure if you tried to connect to a server and received a "No more connections" message from it that you'd rather people stop getting extra clients connected. This is one of the reasons that bots are not allowed on most servers -- the server admins would much rather have their server used by real people rather than just bots.

Secondly, clones are typically used to flood people (then called floodbots). Flooding other people off is a pretty immature thing to do; it only shows you can't handle people even on a medium like IRC, let alone in real life. Flooding wastes bandwidth and contribues to lag, so if you don't like lag (and who does? :) then don't run clones.

Cloners generally get autobanned and persistent cloners will be K-lined or G-lined. Additionally, the sysadmins on the cloner's site will be contacted and action against them requested. This will usually mean suspension or removal of the offender's account. For more information on K-lines and/or G-lines, see the K/G-line document available here.

2.2  What should I do if I'm getting flooded?

Most flooding attacks come from clones - so firstly try to /ignore ALL CTCP (i.e., pings, versions etc.) to stop yourself from getting flooded off. Then do a /whois on some of the nicks that flooded, or if they are already gone (changed nicks) do /whowas (nick). Then get the host (for example, *cnc087034.concentric.net) and calmly report it in #ZT. Please don't paste a long /who output in the channel or in /msg to ops there, for they can all do the /who themselves. Shouting, using colours and otherwise flooding the channel with text will not get you help any faster, and is in fact likely to make them ignore you.

It's usually more effective to have some sort of flood protection, which usually means some sort of script for your client that acts to protect you automatically if you start getting flooded. Some people also just use the step of ignoring all CTCP, which certainly stops them getting flooded. Try asking in a help channel devoted to your client -- see section 5.

2.3  What is a K-line? What is an autoban? What is a G-line?

A K-line is a kill line, which prevents particular user@hosts from connecting to that server. Many K-lines are on a whole provider, so if you are K-lined with the message "clonebots," it's probably not you specifically that has been K-lined, but your whole site or provider.

An autoban means that someone from that host has been mass-messaging or advertising, so they are being automatically banned by ChanSvr (this is short for ChannelSaver, not ChannelServer) or by Uworld.undernet.org when they enter any channel. Autobans last for one hour.

A G-line is a global K-line across the Undernet. Currently, G-lines last for one hour. This is used for persistent cloners. Once again, see the K/G-line document by Moridin for more information.

2.4  Why do I get the message "No Authorisation" when I try to connect to a server?

The "No Authorisation" message also means you cannot connect to the server, but for different reasons. Many servers require that clients have resolved hostnames, so if your favourite server suddenly starts giving you these messages, your provider's DNS server (Domain Name Server) is probably malfunctioning somewhere. There isn't much you can do about it if your address permanently remains unresolved, except maybe to try another server.

2.5  What can I do if I'm K-lined?

Server admins will not remove K-lines without correspondence from that site's administration providing information on how the provider plans to deal with abusive users. Uncooperative providers will not be un-K-lined. To get an e-mail address for the admin on a server, type /admin servername. This lists administrative info for the server and an e-mail address by which they may be contacted.

Section 3

3.1  What are the user modes and what do they do?

  • User modes available: d,i,o,s,w,k
  • User modes are things that affect only you personally and influence what information the server sends you, and which you can only change for yourself, not for others. For example, to turn +i mode on, /mode +i. To turn i mode off, /mode -i. You can also turn on multiple modes at once, or turn some on and others off:

    /mode harry +di Turns on d and i modes for you if your nick is harry.
    /mode johnny5 -d+iw-s Turns d and s modes off and turns i and w on.

    +d  This is (d)eaf mode; you won't see any channel text at all. You will still see joins, parts, topic changes, kicks, bans and other channel mode changes. If someone is usermode +d, then a /whois on them will show a "-" in front of the channels they are in. For example:

    *** Ghostwolf is foxxe@paranoid.wolfspirit.org (Joseph Bongaarts)
    *** on channels: -#chat -@#wasteland
    *** on irc via server BayCity.MI.US.Undernet.Org ([] Concentric Network Corporation)
    *** Ghostwolf is away: /msg will be saved... gone out
    *** Ghostwolf End of /WHOIS list.

    Note that going +d means being "deaf" in *every* channel you are in. You cannot be deaf on a per-channel basis.

    +i  This is (i)nvisible mode, and to answer the obvious question, no, you can't be invisible inside a channel such that no-one else can see you. Suppose icesmurf is +i and in channel #popsicle. Now suppose firesmurf isn't in #popsicle, and does /names #popsicle to see who is inside the channel. Being +i, icesmurf will not show up. Furthermore, suppose icesmurf's /whois address is icesmurf@ppp-643.ihug.co.nz. If firesmurf types /who *ihug.co.nz to see who is on from the ihug host, icesmurf will once again not show up. If firesmurf IS in #popsicle, however, then icesmurf will show up in the /who output:

    * icesmurf @#popsicle Hi icesmurf@ppp-643.ihug.co.nz (I'm just cold.)
    * oozie #chatters_cove H rollin@slip12.ihug.co.nz (Da shlime of humanity)

    This output gives you the nick, the most recent channel they joined and their user@host unless they are +i, in which case they won't show up.

    +o  This is IRC (o)perator, and someone who is +o is an IRC operator. Unlike the other channel modes, this mode cannot be set using /mode +o. If you really are an IRC op, you'll know how to do set this mode on, so I won't bother describing it here. Note that any failed attempts to get IRC operator status by someone are broadcast as a server notice to everyone who has usermode +s (including the IRC ops for that server) so it's not possible to quietly try it.

    +s  This turns on (s)erver notices, which includes notices of nickname collisions, IRC op kills, unauthorised connections, invalid usernames, server clonebot warnings, server splits and connections and a whole lot of other stuff -- quite a lot of stuff, which most people won't really be interested in.

    +w  This is (w)allops mode, which allows you to see IRC op "wallops," which are broadcast messages that they send each other. You don't have to be an IRC op to see these wallops (i.e., anyone can set mode +w on themselves) but note that many IRC ops dislike being msg'ed by non-IRC ops after they saw the IRC op wallop.

    +k  This is a special usermode, available only to services. This currently means the Channel Service bots, X and W. Usermode +k means that X and W cannot be deopped or kicked from any channel. See the section on the Channel Service for more information on X and W.

    3.2  What are all the channel modes and what do they do?

  • Channel modes available: b,i,k,l,m,n,o,p,s,t,v
  • Channel modes affect users in that channel and its visibility. Channel modes can only be changed by channel operators (see below). Any channel mode can be set on using /mode #channel +mode or /mode #channel +mode parameter (if it requires one). You can also use any combination of + modes and - modes in one line.

    +o  This is channel operator mode ("op" or "chanop" for short). An op has the power to change other channel modes -- basically you can't set channel modes in a particular channel if you're not currently an op there. Chanops also have the ability to kick (forcibly remove) people from a channel, using /kick #channelname (nick) (reason). So, icesmurf could do /kick #popsicle lamesmurf you don't like Smurfette! which results in lamesmurf being removed from #popsicle and the following output:

    *** lamesmurf was kicked by icesmurf (you don't like Smurfette!)

    Any chanop can make someone else an op as well, and they will have completely equal power to the original op. Just type /mode #channel +o (nick), e.g., /mode #popsicle +o firesmurf.

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

    /mode #popsicle +ooo bluesmurf papasmurf tallsmurf

    Or deop some people and op others:

    /mode #popsicle +o-oo+o firesmurf dumbsmurf lamesmurf papasmurf

    Now the order of mode change letters becomes important, since the first person specified gets opped, the second and third are deopped, and the fourth is opped. This is because of the order of the mode changes - modes are applied in order to the arguments given.

    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 irc op 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.

    +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 notasmurf, who's not in it, tries to send a message using /msg #popsicle boo! scared ya!, he will get a message similar to:

    *** #popsicle Cannot send to channel

    If a channel isn't +n, then you could do /msg #channelname (text) and it will appear inside the channel as if the person was saying it from right inside -- this is somewhat spooky to see. Note that +n also stops people from doing CTCPs to the entire channel unless they are inside it. If #popsicle is -n, then it is possible to /ping #popsicle without even being inside it. As a general precaution against flooding, and to stop people annoying you with ghostlike messages from outside the channel, it's generally a good idea to set channels +n, and you will find that almost all channels are set +n by their ops.

    +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  This means the channel is a private channel. It does not show up in channel listings and will not appear on a person's /whois info unless the person doing the /whois is also in that private channel. Suppose icesmurf is in channels #popsicle and #smurflove (which is a private channel). If firesmurf (who is not in #smurflove) does /whois on icesmurf, this will be the output:

    *** icesmurf is smurfy@home.mushroom.com (I'm just cold.)
    *** on channels: @#popsicle
    *** on irc via springfield.mo.us.undernet.org (OnTheNet www.getonthe.net)
    *** icesmurf End of /WHOIS list.

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

    *** on channels @#popsicle #smurflove

    +s  This means the channel is a secret channel, which is virtually identical to a private channel. It also does not show up in a channel listing, and not in the /whois info unless the person doing the /whois is also in that channel. The difference is that with private channels, you can /who #channel to see who is inside, so if #smurflove was +p, then firesmurf could /who #smurflove to see that icesmurf and smurfette are inside.

    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:

    *** firesmurf Cannot send to channel

    +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 icesmurf (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.

    +i  This means the channel is invite-only, meaning you must explicitly be invited by an op of the channel, using /invite (nick) #channel. If you are not invited, you will be unable to join the channel. So if #popsicle was +i and icesmurf (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:

    *** #popsicle Cannot join channel (+i) (Invite only channel)

    +l <value>  This means that the channel is limited to a certain number of people. If icesmurf wanted to limit #popsicle to 20 smurfs at a time, he would set /mode #popsicle +l 20. If latesmurf then attempted to join #popsicle when it already had 20 smurfs in it, he would get the following message:

    *** latesmurf Can't join channel (channel is full)

    +k <key>  This means that the channel has a key, like a password, which is necessary to join the channel. If icesmurf wanted to set "brainysmurf" as the password to join the channel, he'd set /mode #popsicle +k brainysmurf. If skysmurf then wanted to join #popsicle, he would have to do /join #popsicle brainysmurf. Note that to remove a keyword (unlock the channel), you must specify the key. That is, icesmurf would have to set /mode #popsicle -k brainysmurf to undo the channel's keyword status and permit entry without a password. If you attempt to join a keyed channel without the key or use an incorrect one, then you will get a message along the following lines:

    *** #popsicle Cannot join channel (+k) (Bad channel key) or
    #popsicle can't join channel (requires the correct key)

    +b  This is the mode used to set a ban, which prevents a particular nick and/or address (nick!user@host) from entering the channel. A banned person cannot enter the channel, or if already in the channel when the ban is set, cannot speak, change nicks, or do any CTCP (pings, versions, etc. to the channel). A ban is of the form /mode #channel +b nick!user@host, e.g., /mode #popsicle ban *!*Gargamel@*.nastyhouse.com.

    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 firesmurf 10. This would set the channel moderated, no external messages, op firesmurf, 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.

    Section 4

    4.1  What is a registered channel? What are X and W?

    X and W are the official Channel Service bots. A registered channel is one that has been registered with the Undernet Channel Service, and has thus been granted the use of either the X or W bot.

    What do X/W do? They will keep your channel open for you (so you don't lose the banlist, topic etc.) and can be set to automatically op you when you enter the channel (if you so choose), and maintain a userlist of those who you wish to be channel ops (who may also be auto-opped). X and W also provide channel security because they enable you to always retake your channel if it gets taken over. X and W have the distinct advantage of being impossible to kick or deop, which makes them very secure indeed. CService also has a pretty decent Web site at http://www.cservice.undernet.org/ which you can check for more information, and which allows you to check the userlist or X/W banlist of a channel from the convenience of a Web browser.

    4.2  How can I register a channel?

    There is an application form on the CService website. Note that CService registers established channels; the registration process is not for creating channels. You will need 10 supporters for your registration application who are regulars of the channel. For more information, ask in #cservice.

    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.

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

    4.3  How do I know if someone is official CService personnel?

    If someone is official CSC personnel, you can type /msg X verify nickname. This will result in one of the following responses:

    If they are a CService admin:

    -X- AnElf!~Palensus@dialup159.apci.net is a CSERVICE admin

    If they are a CService helper:

    -X- Cyke!~cyke@rubicon-79.fuse.net is an official CSERVICE helper

    If someone is both, you will get the following response:

    -X- Super!dglow@calum.csclub.uwaterloo.ca is a CSERVICE admin and an IRC Operator

    If they are none of the above, and just a normal user:

    -X- pretender!fake@anyhost.com is NOT an authenticated CSERVICE representative

    Once again, if you are ever in doubt about whether someone is truly official CService personnel, just ask in #cservice. Note that some helpers are not necessarily official but can be trusted to help you, and you will be told if this is so by the ops in #cservice.

    4.4  What is the difference between a CService admin
    and an IRC operator?

    Everything. IRC ops try to keep the network running smoothly (this is their main role) and sometimes help opless channels and those which have been taken over. Note that this second job is NOT a priority, and IRC ops do this entirely voluntarily -- they have no obligation to help opless channels and those that have been taken over. CService admins are responsible for channel registration and X/W administration and have nothing to do with running the servers.

    4.5  I have a problem with X/W in a registered channel.
    What should I do?

    If you don't know how to use an X/W command, type /msg X help (commandname). So if you needed help on the adduser command, you would type /msg X help adduser to get X's online help. Read the FAQs! They are available on the Web at http://www.cservice.undernet.org/ or via FTP at ftp.undernet.org/irc/docs/cservice.

    If you're not sure whether X is actually capable of doing what you want to do with it, ask in #cservice. As you should have guessed by now, #cservice is a channel for X/W help and information on channel registration. When asking questions in #cservice, please give the channel name, which bot (X or W) and what access level you are so that you can be helped faster. Note that #cservice is NOT for general bot help or bot questions; it only deals with X and W. It is also not for newbie questions or general help with IRC -- try asking in a newbie channel or in #help or #newbies for that, or a help channel for your client (such as #mirc, #ircle, etc).

    4.6  How can I tell if someone really is an IRC operator?

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

    *** Toon is toon@alioth.pi.net (Toon at Alioth)
    *** on channels: @#belgonet
    *** on irc via server Diemen.NL.EU.undernet.org ([irc.pi.net])
    *** Toon is an IRC Operator
    *** toon End of /WHOIS list.

    You can also type /msg X verify nickname to see if someone is an IRC op. For example, /msg X verify wildthang produces:

    -X- wildThang!~danny@internet.chatsystems.com is an IRC Operator

    Some people pretend to be irc ops by putting "is an IRC operator" in various parts of their /whois info. Here is an example:

    *** fakeoper is ~ircop@line911.dayworld.net (is an irc op)
    *** on channels: @#fake
    *** on irc via server Atlanta.GA.us.undernet.org
    *** fakeoper is away: is an IRC operator
    *** fakeoper End of /WHOIS list.

    Note this person has "ircop" as their username, has "is an irc op" in their IRCNAME, and "is an IRC Operator" in their away message. These are 3 common ways of pretending to be an IRC operator. Note that real IRC ops do not like people who pretend to be one, so if you see someone pretending to be one, go to #ZT and mention it.

    Section 5

    5.1  Where can I get general help with IRC?

    The answer to this depends on what kind of help you want. If you are new to IRC, then the following newbie channels are good: #newbies, #ircnewbies and #new2irc.

    Another good place to go is a help channel that is specific to your client. For mIRC, there are many help channels: #mirc, #mirchelp, #mircremote, #mirczone. For wav trading, try #wavs or #wavaddiction. Homer and ircle users should try #macintosh. Pirch users should try #pirch. For help with ircII, try asking in #ircII or in #wasteland.

    As a general guide, if you have a problem with X/W in a registered channel, then ask in #cservice. If you have a problem in an unregistered channel, then ask in a general help channel such as #help or a newbie channel such as #newbies or #ircnewbies. Please don't ask for an IRC op in #cservice, or ask questions on X/W/channel registration in #ZT -- by going to the right channel the first time, you get friendlier help and get it faster.

    Section 6

    6.1  Where can I get a list of Undernet servers?

    On IRC, try typing /map (or /raw map or /quote map) to see a list of currently connected servers. The list is also available on the Web at http://www.user-com.undernet.org/documents/uservers.html.

    6.2  Which servers allow bots?

    The best way to find out is to read the server's message of the day, which many clients automatically display when you connect to the server. Just do /motd servername to read a server's motd. It will almost always display the server's bot policy and what ports they listen for connections on.

    Section 7

    7.1  What should I do if someone is harassing me?

    If someone is harassing you, get their address and /ignore it. If icesmurf wanted to ignore firesmurf, then icesmurf would first get firesmurf's user@host by doing a /whois firesmurf.

    Suppose firesmurf is firesmurf@slip34.mushouse.com. Then icesmurf should type /ignore *!*firesmurf@*.mushouse.com (this works for mIRC, Pirch, ircle and Homer.) In mIRC, you can type /ignore firesmurf 3. In ircII, the correct syntax is /ignore *!*firesmurf@*.mushouse.com all.

    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 :)

    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.

    7.2  What can I do if someone has my nick?

    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 rather than your nick, anyway.

    7.3  I have this problem in a particular channel. Where should I go for help?

    The first thing is to check whether the channel is a registered channel, i.e., does it have X or W in it? If so, then #cservice is the channel to ask what can be done about your problem. If it's an unregistered channel, ask in #help. CService will not op you in a registered channel -- it is the responsibility of the channel manager to control his channel, either directly or through those he appoints to be channel operators. If there are no ops there, then you'll just have to live with it. Use /ignore if it's somebody flooding the channel.

    7.4  I was kicked and/or banned from a channel for NO reason!! What can I do?

    Nothing -- the ops in a channel rule that channel. They can set whatever rules they like for that channel, and kick and ban whomever they like, for any reason or for no reason. If this sounds unfair, then think of a channel as a house. When you come into someone's house, you agree to follow their rules. They can kick you out of the house for whatever reason they like. The neat thing about IRC is that anyone can make a channel -- so just make a channel where you are op and you have your own house where you set the rules. IRC ops will NOT unban you from a channel where you have been banned. Do a /names #channel to see who is inside, and /msg one of the ops asking to be unbanned. If they refuse to unban you, then bad luck.

    7.5  What should I do if we have no ops in our channel?

    If the channel has only a few people (four or less, perhaps), just get everyone to leave, then have a designated person rejoin. Since they are re-creating the channel, the first one to join will be opped. 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 IRC op 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.

    7.6  Someone is spreading kiddie porn and other gross stuff! Who can I report them to?

    No-one -- the Undernet has no policy on content. That doesn't mean that many individual people aren't disgusted by such things (they are), merely that there is no content monitoring by the Undernet. All servers specifically disclaim liability and responsibility for the content of what you are exposed to on IRC, as mentioned in their motd. If you do not agree with this policy, you can always leave IRC by typing /quit. If someone bothers you, then you should /ignore them.

    Remember that any transfer of any data or files via DCC is, by definition, bypassing all the Undernet servers and connecting directly to the other person's machine. Thus no pictures, wavs, etc. are ever transferred through the servers or the Undernet network in general. See the Undernet Legal Issues FAQ for a more thorough look at the issue.

    You should always be careful when accepting DCC sends from people, and do not auto-accept DCC sends or autojoin on invite. That's just asking for trouble.

    Section 8

    8.1  How do I become an IRC operator? or I'm interested in running my own Undernet server. How can I do that?

    The short answer is run an Undernet server. And let's start by saying that ircd (the server program) runs only on the various flavours of Unix. Then you must fill in the application to link the server to the Undernet and mail it to routing-com@undernet.org. Running a server requires a powerful machine with lots of RAM, usually almost dedicated entirely for that purpose. Also, proposed new servers must have really good links -- better than a T1, plus good ping times to the hub servers. To find out what the current hub servers for the Undernet are, e-mail routing-com@undernet.org and ask.

    Section 9

    9.1  What mailing lists are available for the Undernet?

    user-com@undernet.org the Undernet User Committee, the voice for users on the Undernet.
    promotions@undernet.org promoting the Undernet to current and potential users.
    help@undernet.org general IRC help.
    documents@undernet.org discussion (and doing, hopefully ;) of the updating of the Undernet's documents.
    cservice@undernet.org general registration and X/W problems.
    coder-com@undernet.org discussion of Undernet server coding.
    routing-com@undernet.org new Undernet server applications and discussion on the Undernet's routing.

    Section 10

    10.1  You haven't helped me. Where should I look?

    Try the monstrous Undernet FAQ; it covers a wide range of issues not covered here as well as some that are. Being a general document, it can't cover things in excessive detail, so see the Undernet Documents Project website, which has explanations of lag/netsplits, CTCP, DCC, and also the technical RFC (1459) for the IRC protocol between clients and servers. See also:

    Or try asking in general help channels on IRC such as #help or #newbies. Happy IRC'ing!

    Once again, any comments/additions/corrections/money should be sent to loki@undernet.org. Please do NOT e-mail me asking for help with IRC; I don't have the time to answer and get enough mail as it is. Please e-mail help@undernet.org instead.

    Permission is granted to transmit and reproduce this document in electronic form, as long as it remains unaltered in any way.

    Return to main Documents Project page