Edited and maintained by

Tracy-Ann Powell
tracyann@ihug.co.nz

CUSTOMERS
2.1 THE MANAGEMENT STRUCTURE AND THERE JOBS

SECTION 4 - Getting op(s) (the @) in front of your name
4.0 GETTING STARTED
4.1 SETTING THE PASSWORD
4.2 LOGIN ON
4.3 GETTING OP(s) STATUS ON THE CHANNEL

Hello, my name is Tracy-Ann (nickname tracy{JR}), I'm a creator and channel co.-owner of the channel #TSA_list, which is located on Undernet. Since, 5^th October 1997 #TSA_list has been a registered channel of Undernet. Which basically means that we are supposed to be able to get support from Undernet if we have problems . . .

This document is to explain the information that a channel operator (or op. For short) will be expected to do, learn, and understand for them to do their job probably on #TSA_list. This document will give a brief history of the channel, information on the BOTS (automated programmes that monitor the activity in the channel), information on the rules and protocol that is expected of our channel op(s) and a guide on how our channel op(s) can handle certain problem they may face while on #TSA_list channel.

You MUST read this document if you are a channel operator on #TSA_list channel, or about to become one.

To start I would like to quickly, and briefly, explain a little of the history and the idea behind #TSA_list channel. I will give you a little back ground information on the way the channel was created, where I got the idea, and what philosophy was used to create the environment that you can see in the channel now (in a normal day .)

After writing my first story for the list I was stunned by the way that many people helped me on, to feel like I could write other stories for the list. I was using IRC very much at this time, and was a channel op in three other channels. Yet, I had not had an interest to create my own channel at the time, so I was still only interested in being an op in others channel (which I was for about 2 years). Finally, after a few months on the Transformation Story Archive talk list I knew that I wanted so much to talk to the other authors and people from that list, in ‘real time’. The best way of doing that was to create a channel, where anyone of the list could come to the channel and talk to each other. As of that date, #TSA_list was born.

The channel was not a hit right away. In fact, it got some very negative feedback from the list, feedback, that should have stopped me there and then from continuing my dream of this channel. However, I ignored the negative feedback, and listened to some of the positive feedback I got. One such feedback came from my now best-friend, Dana (nick name Zuul) His email pushed me on to finally totally ignore the negative feedback, and push towards sticking around 'everyday and night' waiting for people to come on. Finally, a small little group of people came to the channel, and from that day the channel became family. Kpack, Winc, Dana, Daniel_San, and Wildstar.

While the channel continued along in that family, for a while, I was busy creating life in a BOT called Genie_b (for the rest of this document, all further talk about the Genie BOT(s) will be made as just Genie.) This BOT was to interact between the people on the list and the commands that could be given. It was also to automatically op the people who were now the official channel op(s). Finally Genie went on line and there was many problems with her to start with. However, with the help of the family that had come to the channel, Genie became stable and another member of the family. Finally, Dana took over the running of Genie, and with that, also became the co.-owner of #TSA_list.

The channel has grown much since then, watching people come and people go. Dana and myself took a step back and became like the CO's of a corporation, letting our responsible channel managers and channel op(s) use the channel and manage the channel as it is growing with their needs, and the needs of the very large family that is using the channel, through the day and overnight.

Then, after almost a year of being active, the channel finally became registered as an official Undernet IRC channel.

Genie has become a great granter of wishes (sometimes). Using a great written program by Dana to grant wishes of the people on the list, transforming people into many kinds of beings that one can think of (well, at least in IRC mode anyway ) which has brought many people to the list, just to play with Genie.

However, one of the greatest things about #TSA_list is the fact that the authors who write transformation stories on the net (and a few who have been published also) have been able to talk about ideas, plots, character building, and many more things that have brought about the creation of some very beautiful and wonderful stories that have hit the net and the TSA email list.

No matter who you talk to, the #TSA_list means many things to nearly everyone on the channel, and to those that have come and gone.

The philosophy of the #TSA_list is a simple one however. It is a place where people can enjoy themselves, get to know people, and they themselves know that the channel is a peaceful and safe place to discuss their wildest (non-sexually, and usually transformation related) fantasies. We pride ourselves on allowing people to have a freedom of speech, but also on the fact that we do not allow racist, nasty comments against others to be ignored. The channel owners, managers, and op(s) are an integrated unit, that work together to protect the channel from spammers, HNG's (Horny Net Geek's) and flooders. To insure then all the people using and frequenting #TSA_list are able to enjoy themselves without the problems of dealing with those kind of people by themselves. However, the channel owners, managers and op(s) know, that the channel is there for them also.

Just what is the meaning of Owner, General Manager, Manager, Operator (op) and Customers when you are talking in the content of IRC. Well, to explain that I will give a brief outline of what it is in a company environment (such as Quality Hotel ltd. chain).

An owner(s) of the company (CEO etc.) is the person(s) who controls the running of the company from outside the working environment. They deal mainly with the things that effect the business in big ways. As with the #TSA_list, Dana and myself, run and deal with the problems that (hopefully) no-one inside the channel will have to deal with. We also try very hard to create added extras to the channel, like the Undernet #TSA_list webpage, the #TSA_list Newspaper, the Genie and other such projects (some still in the works, some about ready to come out). It is Dana's job (because he is bloody good at it) to edit and control Genie. This is a full time position for Dana, as he is also working two other jobs that gets him money. Editing, fixing and updating Genie is an unpaid job, as with everything else the mangers, op(s) and I do for this channel. Dana, like us all, do it because either we want to, or for the love of the channel (maybe the same thing.) I, as the other CEO of the channel, create the added background to the channel and create the rules and very firm hold this channel works under. Designing extra things that will be added to the #TSA_list in the near future. However, even though both Dana and I can not spend much time on the channel, both Dana and I are very approachable and easy to talk to. (Not, like the CEO(s) of some of the bigger companies in the world, hey ) [W.Level 500-490]

A General Manager(s) of the company is the person(s) who manages the company's interests within the guidelines of the CEO, for the people using the company and the employees. They do about the same as a CEO of a company, dealing with bigger projects that require extra work outside of business hours. They are also the first people who deal with employer disputes and with the responsibility to make sure they are themselves informed with everything that goes on within the company, from small events to very large events. In #TSA_list the General Manager(s) of the channel is a person who makes sure that the normal running of the channel is being followed. The General Manger(s) have to maintain a working environment between employees (Managers and Op(s)) and the customers using the channel. The General Manger's job requires him/her to deal with problems that require someone with high level within the W BOT. Also, the General Manager(s) is the first person to have to deal with Op(s) and Manager(s) disputes and have to work towards resolving them disputes so they do not effect the running of the channel, or our customers. In the channel, the General Manager(s) must also be approachable, and able to talk with all other people like an equal and not like their 'boss'. [W.Level 480-400]

A Manager(s) job is to be the first line contact between control of the business, making sure everything is getting done and working fine, and the happy running of the people who are working for the company. The Manager(s) must make sure that their team of workers (employees) are able to do their job, and if they can't then the manager informs the general manager how the job could be made easier. Furthermore, the Manager(s) of a company is expected to interact with the customers as a friend and be willing to work along side the employees to create a better environment for the customer. The Manager(s) of the #TSA_list channel are the people who are first to deal with some of the very active problems within the channel. They are excepted to be in operator status (op'd with a @ in front of their name) every time they are in the channel, as with General Managers and Owners. It is their responsibility to be seen as a backbone of the important management structure of the channel. Their duties range from keeping peace, dealing with spammers, flooders, or HNG(s) to even having to create ideas that could make the #TSA_list more interesting to people, and bring more people towards the channel. They are the people who are on the channel the most, and understand the idea of how the channel is important to everyone who is there, and is willing to keep the peaceful environment that continued to grow from the channel's first days. [W.Level 399-200]

An Operator(s) (or otherwise known as Duty Manager, and Assistant Manager) job is to be in the forefront of the customer and business contact. They are the people who keep peace, and manage the business while the other managers are out of the company, doing other things (or are sick, or on a holiday in Disneyland or Hawaii ) The Ass. Managers of the channel are the people who are in operator status when Owners, General Managers, and Managers are not on the list. They are made operator by using Genie to give them operator status. When in operator status they have the same responsibility to monitor the channel, and to deal with spammers, flooders or HNG(s) as a Manager, General Manager, or owners. However, for the Duty Manager(s) of the channel, he/she does not have to become a operator if they don't want. They are expected as Operators to have a sense of responsibility for the channel, and an interest to see the channel better itself and want to see that growth of the channel continues towards a better environment for our customers and everyone else involved in the channel. They also have the responsibility to look after the channel's interests, and be active in supporting and helping the management with the running of the channel. [W.Level 199-100]

A Trainee is someone who will be training for full W access. This will include getting operators status and the little @ in front of their names when they are required to be op(s). It is their duty to learn, watch and sometimes (especially when one of the other operators' or higher isn't on) ban and kick people off the channel using W bot. These people do not right away get ops' on a channel, not until the front line staff (operators and Managers) think that the person is ready and capable to take on the position. There will be about 3 trainees' at any one time, these people will learn how to use the bot(s), the rules of the channel, and even how to do specialist jobs like maintaining WebPages, or news lists. [W.Level 99-75]

A Customer is the one person that makes a company work. Without the customer, there is not company. They are an integrated part of each other and both have to have a respect for one and other to be able to enjoy each others services. A Customer in the business since is the person who benefits from the job of the company. The company also benefits from the customers interest in the company, depending on the business, depends on the way that they benefit. Our company (the #TSA_list) benefits from our customers by becoming a great 'bar' like environment for people to visit. With each customer that is happy with the environment, then they will bring more people to the channel. The more people in the channel, the better the channel is and the greater the knowledge and exchanged ideas are (the more friends are made, and the world becomes a better place for it ) The customer also has a responsibility to the channel. Rules and important things they must consider when they are using the channel (these are listed in the house rules section of this document.) Without these customers, we would not have a channel. [W.Level 49-0]

Due to changes in management structures and positions of people I will not be including a break down of the people in management in this document file. However, there will be a weekly email list to all people within the Management structure (an employee email so to speak) that will have the current structure and any other important information in it.

Zuul and myself have kept this structure open to a lot of interaction between customers and owners. All major changes to the channel will be considered by the entire management structure and we will also get the input from our customers, since they are using the service also. This means that an email list of all the management people is required to be maintained whenever someone new joins the management level. I believe totally in free speech, so if someone wants to make a comment about anything, it is better they make it then let a possible good idea be wasted.

Being an operator, no matter what position one has, is an important job that must be taken seriously at all times. As a few operators have found out through unfortunate situations, being a operator sometimes targets you for abuse and problems from people inside and outside the channel. Unless you can deal with the bad moments as equally as you can deal with the fun moments, you should think twice about being an operator on IRC.

However, once you are an operator on IRC, and you are in one of the above positions, your activities within are to be focused on the aims and philosophy of the channel. To make #TSA_list a place where people can enjoy themselves, without worry of nasty comments or racism against their believes, fantasies, or personality.

The responsibility of the operator(s) is to make sure that they continue to enforce the house rules of the channel, and also activity support and bid by them same rules themselves. Only then, is the operator proving that the house rules are effective to everyone, including our customers.

Before you can use W with your operator(s) account, you must first set the password for your hostmask (account name) To do this you must message the W bot to set your password. This you do by the following command (password must be 6 letters/numbers or more):

Once you have set your password, you will need to LOGIN to W every-time you join Undernet. If you don't then you will not get Autoop'd or op'd by W until you have logged in. To do this you should set your Undernet program to automatically send the following command every time you join Undernet:

There are ways to have your computer program (Pirch and mIRC) to automatically send this message to the W bot as soon as you log on to Undernet. However, I would advise against using this, if you have someone else who can use your computer, as that could allow them to gain access to operator status on the channel.

Once you are in W bot and have set your password. There are two ways that you can get OP(s) on #TSA_list:

All these positions are AUTOOP(d) by the W bot. However, if the W bot is not on the channel, soon there will be a function in Genie that will allow you to gain op's on the channel like with W bot. More on that in future updates to this manual.

You mainly gain op's status when there isn't many other ops on the channel at one time. The maxium normal running about of op's on the channel is about 1 op to every 5 users. This is to make sure that there are not too many op(s) on the channel at one time. As owner(s) of the channel, Dana and I request that #TSA_list does not get too operator heavy (meaning that newbies will come to the channel and not get the feeling that everyone is judging them.)

You can gain op(s) by using the OP command within W bot:

This following is a list of the commands that are included within the W BOT that is always (when not split from server ) on the #TSA_list channel. This BOT is the property of the Undernet managers and owners, and with the use of this BOT why have certain obligation that we (as a channel) must also fore-fill (explained in Appendix(s).

NOTE : the variables AlwaysOp, UserFlags, MassDeopPro, NickFloodPro, URL and description can be changed by someone with 450+ access on your channel.

Variables for SET

MassDeopPro : The maximum number of deops X will allow in a 15 sec period. Any user exceeding this will be DeOped and Suspended (if on the userlist).

NickFloodPro : The maximum number of nick changes that can be done in the channel in a 15 sec period. Any user exceeding this number will be kicked from the channel and suspended (if on the userlist). NOTE : The .noclones patch makes this variable obsolete, since it will not allow rapid nick changes.

FloodPro : The maximum number of KICKs, TOPIC CHANGES and such that can be sent to the channel in a 15 second period. Any user exceeding this limit will be kicked and suspended (if on the userlist). NOTE : This does NOT work against normal channel dialogue, since X/W are +d (deaf) to all channel text.

UserFlags : Set's default user settings that will be given to a new user on the channel. Default value is 0.

0 = AUTOOP OFF for new users

1 = AUTOOP ON for new users

NoOp : In this mode X/W will deop EVERYONE. Making them the only op in the channel. However, users may still access commands though X/W.

AlwaysOp : This variable insures that X/W will always have ops. They will op themselves if it is not given to them.

OpOnly : Make op the only chanop command available though X/W. Also, you can ONLY op yourself. NOTE : This does NOT prevent someone withops in the channel from exercising op commands themselves.

StrictOp : In this mode only people on the userlist may have ops. If they are on the list, they must send their password before they are allowed ops.

Lang : Changes default language for the channel.

en (english)

nl (dutch)

fr (francais)

ge (deutsch)

Description : Sets the default channel topic. This does NOT affect the actual channel topic. The topic can be see only in the chaninfo, or on the webpage.

URL : Sets the default channel URL. This can be seen from the chaninfo, or the webpage.

AutoTopic : This flag makes X or W reset the topic to the channel URL and Description very 30 minutes. Note that if the channel is idle, the topic will not be reset during that time.

ADDCHAN: syntax - /msg X,W addchan #channel : Adds the channel to X/W's database and sets channel default modes. If you do not use this command after you join X/W to your channel they will not rejoin after a restart ect.

JOIN : syntax - /msg X,W join #channel : Tells X/W to join your channel. Enough said ;)

PART : syntax - /msg X,W part #channel : Tells X/W to part your channel.

REMCHAN: syntax - /msg X,W remchan #channel : Removes your channel defaults from X/W's database. Useful when you want to change default modes. This is NOT the same as a purge of your channel. X/W will not rejoin unless you readdchan after this.

CLEARMODE : syntax - /msg X,W clearmode #channel : Clears all channel modes. Useful when a channel has been locked up. (set +i or +k without your knowledge)

MODINFO : syntax - /msg X,W modinfo #channel <variable> <user> <newvalue> : Changes a user's access settings

Access : Changes the access level of a user, possible values are 1 - (1 level below yours). So if you are 400, you can give up to 399 access.

AutoOp : Changes Autoop from ON to OFF. Autoop means that X/W will op the user when they enter the channel, provided they have logged in.

Match : Changes the user@host for a user in X/W's database. Useful if a user on your channel has changed ISP's Example : /msg X modinfo #somechannel MATCH someuser blah@blah

RemPass: Removes a users password. Yes a manager can remove his/her own password, he/she just has to be verified first. Example : /msg X,W modinfo #somechannel REMPASS someuser

REMUSER: syntax - /msg X,W remuser #channel <nick> :Removes a user from the channel database. You must have higher access than the user you want to remove.

STATUS : syntax - /msg X,W status #channel : Displays all special X/W modes, Channel modes and the number of users in your channel. Neat huh :)

• Level 100-399 : Channel Managers

DEOP : syntax - /msg X,W deop #channel <nick1> [nick2] [nick3] .... : Deops one or more persons in you channel.

INVITE : syntax - /msg X,W invite #channel <nick> : Has X invite someone in your channel.

OP : syntax - /msg X,W op #channel <nick1> [nick2] [nick3] .... :Ops one or more persons in your channel

SUSPEND : syntax - /msg X,W suspend #channel <nick|user@host> <duration> s,m,h or d : Suspends a users access to X/W for the specified period of time. s(econds) , m(inutes), h(ours) or d(ays). You can only suspend someone with access lower than yours.

UNSUSPEND : syntax - /msg X,W unsuspend #channel <nick> : Unsuspends a user on your access list.

• Level 75-99 : Trainee

BAN : syntax - /msg X,W ban #channel <nick|user@host> [duration in hours] [level] [reason] : Bans a person on X/W's list for a specific number of hours. The max is 8760, 1 year. You use the person's nick if they are online. or specify a user@host if they are not. Level can be from 1 to your access level. A level 20 - 74 ban prevents the user from having ops. 75+ keeps them from being in the channel at all. You must at least have the same access level as the level of the ban to remove it.

UNBAN : syntax - /msg X,W unban #channel <nick|user@host> : Unbans a person from your channel. By nick if they are online, or by user@host if they are not, as with ban.

KICK : syntax - /msg X,W kick #channel <nick> [reason] : Tells X/W to kick somone from your channel, The reason is optional. Your name will be placed in the kick msg.

SEE KICK NOTES:

TOPIC : syntax - /msg X,W topic #channel <newtopic> : Has X/W change the topic in your channel.

STATUS : syntax - /msg X,W status #channel : This does the same thing as level 400 status EXCEPT, it will not report channel modes (+nt ect) to anyone with access below 400.

• Level 0 : Everyone on the channel
  

ACCESS : syntax - /msg X,W access #channel <nick|search string> [options] : Can look up the access for a certain person or a string. Expl : /msg X,W access #channel *!*@*.gnn.com , would return all GNN users with access on that channel. Also you can use these options instead of a nick or string.

-min level - show only users above the given level

-max level - show only users below the given level

-autoop - Show only users with autoop on.

-noautoop - Show only users with autoop off.

-modif - Shows who last modified the access listing

Access Flags : - output of access command

-X- USER: Blahguy- (*!*username@*.blah.com) ACCESS: 1 LMPU

-X- CHANNEL: #cservice -- AUTOOP: ON

M = Modified, but not saved to disk, database is autosaved every 90 minutes.
P = Has a password.
U = User is currently authenticated.
L = Loaded in memory, An access remains listed in memory for 90 minutes after you log off.

BANLIST : syntax - /msg X,W banlist #channel : Shows the channel banlist. You must be in the channel to use this command.

CHANINFO: syntax - /msg X,W chaninfo #channel : Displays whether or not a channel is registered, and to whom.

DEAUTH : syntax - /msg X,W deauth #channel : If you have sent you password already and would like to deauthenticate yourself. Use this command.

HELP : syntax - /msg X,W help [command] : Displays help file on a given command.

LBANLIST : syntax - /msg X,W lbanlist #channel <search string> :Searches X/W's banlist for a certain string. Use * to see the whole list.

LOGIN : syntax - /msg X,W login #channel - If you have no password. /msg x@channels.undernet.org login #channel <password> - if you do /msg w@channels2.undernet.org login #channel <password> - for WThis loads your access listing into memory and authenticates you on your channel. Note : Exact same as pass

MAP : syntax - /msg X,W map : Shows a map of connected servers.

MOTD : syntax - /msg X,W motd : Displays X/W's message of the day.

NEWPASS : syntax - /msg X@channels.undernet.org or W@channels2.undernet.org newpass #channel <password> : Sets a password on a channel for X/W. If it is X send to X@channels.undernet.org. If it is W send to W@channels2.undernet.org.

PASS : syntax - /msg X@channels.undernet.org or W@channels2.undernet.org pass #channel <password> See Login

SHOWCOMMANDS : syntax - /msg X,W showcommands #channel : Shows all commands you can use on a channel.

SHOWIGNORE : syntax - /msg X,W showignore : Shows X/W's ignore list. This is what happens when someone tries to or accidentally floods X/W. The time length is 60 minutes.

VERIFY : syntax - /msg X,W verify nick : Displays whether or not a person is an official cservice rep. If X/W answers that the person is "NOT an authenticated CSERVICE representative" please come to #cservice and ask about them.

As of November 1st 1996 passwords are mandatory for ALL users. Users without passwords may still login, but will be restricted to level 0 commands (this includes newpass) until they set a password (see newpass).

5.1 GENIE BOT COMMANDS AND INFORMATION

These are the current set of Genie-Bot commands, for any Genie-Bot with a Core Date of October 1, 1997, or later. While many of these commands are tied into channel levels, they do pose some level of compromisability, and thus they are NOT for general distribution, but rather are meant as EYES-ONLY information for Genie's Authorised Users. Please be careful of not only the distribution of this file, but the open use of these commands, by using the /msg command where applicable.

Rules are not a term I like to use lightly, however, every good playground or bar requires a set of house rules and things that must be followed. As Operators/Managers of the #TSA_list channel, it is your duty to make sure that the rules and guidelines that are discussed below a followed. However, this is not the military and you can sometimes be able to us your own judgement on whither the breaking of a rule should be followed up. There are a few that no matter what you judgement says, MUST be dealt with right away, for the safety of the channel, our customers and yourselves.

After you have had to deal with a problem, you must follow the requirements the are listed under each of the rules and problems. It is always a great idea to let all the other management know about anyone that has been a problem. The best way to do this is to email everyone on the TSA Management list that you have got. This will mean all the people on the management team will know to keep an eye out for that person again. Do not just supply the nick, also supply the hostmask of the person. The hostmask is the thing that shows up when you do a /whois on the person's nick. Ie:

Melon[p5647-predge-jig.afg.husdon.net]

This nick of the above is Melon the hostmask is the information inside the brackets, which is the information on the person's server address. You can also find this on the log (you have to be making) of #TSA_list which will show them joining the channel at some stage.

Keeping the other management staff informed means that we can stop this person playing everyone for a fool and also means we can contain a problem from getting to big.

Also, where required it would be a good idea to email the owner(s) and General manager(s) the log of the time the problem happened. This will mean the Owner(s) and GM(s) can decide if it is worth following up with the CSC.

Once you have kick and banned someone from a channel, you may have angered the person. If that person has it in for you, they may attempt to flood you off Internet as a sign to say, "I'm one better then you."

To prevent this from happening you have to make sure you have a flood protection script, also, you have to make sure that you have set mode +I when you log into IRC. +I makes you invisible to anyone who doesn't know your exact nickname.

So if you have made sure you are +I, after you kick / ban the #nick, you can then change your nickname to something else, something that people would find hard to guess. Then, you can prevent someone from finding you. They have to find you, to flood you.

It is not always easy to know when the channel is being flooded. There is a script I will be finishing soon that I will be giving to all my high-op(s) that will show when someone is flooding the channel.

Most people don't even know what flooding is, so I will quickly explain in 'laymens' terms what flooding is.

CTCP floods are the most basic type of flood. The idea behind a CTCP flood is to attempt to make somebody send enough bytes to their server in enough seconds to be disconnected for flooding. However, you can be disconnected also if you send to many bytes yourself. Therefore, you want to send the CTCP that will give you the largest number of bytes in return, which is usually VERSION.

One reason why CTCP floods suck is that almost everyone runs some type of script to protect from these types of floods. Weak scripts can still be flooded and some people run no protection scripts at all (usually people to new to IRC to know any better).

This is why it is a good idea as a operator on a channel, to get a script file that protects against CTCP floods. I am using Little Star which I believe is a very good mIRC program and script. However, it takes up a lot of space on the hard-drive and requires a expert to know everything that is use-able within that script. Other scripts are available on Internet, and there are good small protection scripts out there, that will protect you from CTCP flooders.

I would make the suggestion, as the co.-owner of #TSA_list, that you find yourself a good protection script, that will also monitor people who flood your computer, using CTCP or hacker scripts. So far, the only well worth using program is Little Star, so if you are on IRC a lot, I would highly suggest downloading that. However, I would like to know if you do go to use that program, so that I can inform you about what options are not required in #TSA-list.

TEXT flood is when someone attempts to flood the channel with text. These people are attempting to get someone's own program to lock-up through do much happening at once. If your computer gets to much information at once, your system will start to decrease in speed, and if the flooders are lucky, your system will be unable to respond to your next ping request in time, and then your server will kick you as a ping time-out.

This ruling is very simple. It is not allowed at all. It is a no-no, it is a kick/ban offence and if anyone has a problem with that, you can give them my email address and I will explain it even simpler to them

Well, this is not the easiest thing to answer. Usually you can first tell you are being flooded by lag. Great lag, means that something is getting your IRC program to respond to a lot of CTCP information.

Another one is if you start seeing people stop talking and then finally they are ping-timed out. If you see many ping time out within a few minutes of each other, you will know that something is flooding people off IRC.

The other one is if you see #nick posting many lines of words, one after the other within a quick time. This is a indication that that #nick is attempting to flood the channel.

No matter how you look at it, it is very hard to pick out the flooder, unless they are doing it to you.

If you have a feeling that someone is flooding. You most do the following:

say on the channel

#nick are you flooding?

If after a few moments you do not get a reply to this, and it still continues go to 2.

then

However, if you KNOW that someone is flooding, do step 2 right away. I would more like to explain that you were wrong and kicked someone for false flooding, then to here from someone that the channel was no under the control of mad morons from space

This is simple. You go to the channel #wasteland or #cservice and talk to one of the operators there. At #wasteland you will find the IRCop(s) and it is there job to stop hackers and flooders from taking over registered channels.

You explain to them the problem, and as for their help. Most of the IRCop(s) will help out, and remove the problem from the channel.

This is something I would require you to do, as soon as you think the flooder or hacker problem is getting out of hand.

To follow up a flooder problem, is a simple factor of send Channel Owner(s), and General Manager(s) a copy of the log files required to prove that the person was a flooder, or of the instant in mention.

This is so they can do follow up on flooder problems.

First of all, a little explanation on just what a HNG is. Quiet simply, they are people who want nothing but to do cybersex with people. Usually they are young teenage males, who have nothing better to do with their time and go out of their way to cause problems for other people.

Spammers are the ones that want nothing more then to come into a channel and make themselves a pain by bringing up any other topic, but the one that belongs on the channel. #TSA_list is a channel which is about Transformations and the stories that are about transformations, however it is not against the rules to talk about a topic that isn't about transformations. Hell, we talked about my engagement for about three straight hours on the channel when it first happened. However, there is a difference between the regulars chatting about their lives, and someone who is a newbie and comes in bringing up any topic but the one that is wanted. Sometimes even though this people are spamming, they can sometimes not know it is wrong, so we have to be very careful.

Now, even through both are usually teenagers who are just being little assholes, they can become a very bad problem for a channel, and if they are very much upset they will make themselves even more of a pain. (Take it from me, I have dealt with them enough ) So dealing with the little shits, is a very delicate manner of escorting them to the door and if they don't go, showing them a little more forcefully.

If people start asking the following question on a channel like ours, you tend to know right away they have one thing on their mind:

Anyone for sex?
Any sexy babies want to give me your picture?
I like to play, who wants to play with me?
I'm a man, all man, very long man, who wants to . . . .

I think you can get the point. If people come in and start messaging others for sex, or other things of that nature, they are not wanted on the channel while they keep up that type of attitude. That is what a HNG usually looks like, however if you also get completes from the regulars that #nick is messaging them for pictures or sex, then you also know that they are probably HNG's who know not to advertise on the channel.

Now, spammers are also very simple to spot, but, one most be very careful not to get just off topic chats mixed up with spammers. The following is a spammer that I logged a while back:

<Kill> So why is the moon yellow?
<Tree> I know what you mean Mcin, it is getting hard to think of something different to write.
<Winc> Because it is. Hey, Mcin have you been able to get that story written yet?
<Mcin> Not yet, Winc. But, I'm trying to finish it.
<Kill> Why did starwars have a Jedi in it?
<Mcin> I am stuck on the problem that is causing my story to feel unfleshed.
<Tree> I know that problem Mcin. I have just finished ********** and I can't get the thing to end.
<Kill> But, how do you use a computer?
<Winc> Kill please, bring your chat to the topic at hand. If you don't have anything to add to the topic, then please bring up something to do with transformations and or stories.
<Mcin> I was wondering when you were going to tell Kill off.
<Winc> Kill are you on the TSA email list?
<Kill> What is a tree?
<Tree> Kill try Genie, what is tree and you will find out.
<Kill> No, Winc. But what is a cat doing in my room, who am I? Am I a tree?
****Private chat to Kill***** Please keep the chat to topic, or you will be escorted out of the channel
<Mcin> You just can't help yourself can you Kill. I wouldn't push Winc, she has had a bad day :-)
<Kill> Yes, but I have a pin in my foot. I think it hurts but what is pain anyway. I am a god.
<Winc> Will I'm the owner of the channel, and I eat gods for breakfast. Bye, Bye Kill.
Mode set +B Kill<something@somethingelse.geekmood.net>
***Kill has been kicked by Winc --- God go play in your own box ***
<Mcin> Once again, Winc gives a serve and the kick/ban was so entertaining. You know something, Winc, you know how to make people laugh. "I eat gods for breakfast" good one :-)
Winc changed nick to Dayafter

As you can see, Kill just won't stop chatting about things that had nothing to do with the topic, or with the channel. However, if Kill had turned around and said that it didn't know what to talk about, we could have brought him up to date with the topic, as I tried to do by asking him if he was on the TSA email list. Just remember, some people are new to IRC, so they really don't know what to say on the channel. Some people said saying stupid things to see if people will talk to them. We first have to make sure that the person knows they are welcome to talk, but, if they don't tow the line, then ban them and kick them off the channel.

Well the first thing you have to do is talk to them in a private message bases. Query their nick and talk to them, outside of the main channel. HNG's love to show off and they do that if people on the channel said telling them what to do.

If they start getting out of hand and start causing problems with the regulars to the channel, basically kick them off. Then explain to them that the channel is not a place for people who want to talk about sex and childish topics like (whatever else they were talking about)

It is in the manner you talk to them. If you get angry with them, they will just think it is funny. A child loves to see fireworks, so if you show fireworks they will want to see more. The way I usually deal with them is to 'calmly' tell them that our channel isn't really a place where we tolerate that kind of attitude. Also, tell them that they are welcome in the channel, if they keep to the topic and start acting like responsible people. Many times, they get smart about it, but after saying that I place them on ignore, so that I don't have to worry about them, until they come back to the channel. Once they come back into the channel, I place them of ignore and monitor the way they interact with others. Most of the time, they get bored, leave and never come back. Some other times, they show they are very interested in the topic and become a very active and welcome member of the channel group. Other times however, they don't know when they have been given a chance and blow it again. They are then kick, banned off the channel, without explanation. Them type are the ones you really don't want to pay attention to.

The same really applies to Spammers. However, as I have shown in 6.4.2, it is always a good idea to make sure that the person isn't just a newbie to IRC, or Internet. There are a few people out their who are also from the email list who only know about email and have yet to get a hang on the great forces like, IRC

It is always a good idea to make sure that all management staff know of HNG's, now matter how silly and harmless they have appeared to be. Even the most harmless can turn out to be killer hackers and are just waiting for a chance to deal a nasty blow to Genie or everyone on the channel. The more information the management have, the better it they will be to deal with any other problem that comes from HNG's and Spammers.

This is one of the hardest to deal with when you are a channel op. One of the reasons I am now using Little Star. Illegal channels are channels that we do not allow people to be on, when they are on #TSA_list.

Most of the times that means you have to manually do a /whois on the person and make sure they are not in any of the illegal channels.

The reason to stop people in illegal channels on to #TSA_list is because other people do a /whois on that person, see #TSA_list in their information and then follow them to our channel. This isn't a problem, unless that person is on a warez channel, which could mean we can get anywhere from 10 to 50 people instantly joining the channel.

Not everyone needs to be checked, however, it is always a good idea to keep an eye on the regulars also. Not to be a pain, but, not everyone on the channel knows what channels can cause us problems.

When needing to check newbies, wait to see how long they are on the channel. If they stay for a little while (about 5 minutes) then it would be a good idea to do a /whois on their nick. Then you know if they are in any other channels. Judging from what channels they are on, depends on if you have to do anything about it.

Anything that has the following in it is a no, no:

sex
warez
kiddie porn
porn
adult picture
animal sex
XXXXXX

I think you can get the hint on what channels are not allowed to be in their /whois information.

The best way is to first private message the #nick and tell them that they have to leave the bad channel, as it isn't allowed in #TSA_list.

However, if it gets to be a problem, you ask them on the main channel to either leave <the bad channel> or leave this channel. Then if they ignore you, kick them off.

It is not always a good thing to kick fast. Sometimes it is better to explain why we don't want them channels, or have time to deal with the problems they can cause. However, one most also see that the moral reasons involved can also come up. It has happened before that a channel operator got to involved in trying to get this person off the channel, that they got into a fighting match about what is wrong with kiddie-porn. I'm not going to get into what was said, but I will say, that all this does is cause problems for the operator, who should be paying attention to the channel and not to someone who could just as simply be kicked off the channel. There is no use arguing a point like kiddie-porn on IRC. They ignore you anyway when the crush comes to the crush. (long lessons that I have had to learn the hard way I'm afraid to say )

Basically this is a NO, NO. As a channel manager, you are to make sure that none of the other channel managers' deop/kick/ban W or Genie Bots'. This is considered abuse and will be dealt with severely and can result in the removal of W from the channel and the removal of the channel manager from the channel also. "Testing", such as seeing what will happen if W or Genie is deop'd, is considered abuse. If Genie is playing up, then Genie is required to be asked to leave using the level 7 command to make sure genie leaves the channel. (See Section 7 on Genie commands). However, W Bot is NEVER asked to leave by anyone on the channel. If W is playing up and do strange things, you are to report the problem on the channel #Cservice and by emailing the General Manager(s) and Owner(s) of #TSA_list. Emailing General Manger(s) and Owner(s) of the channel #TSA_list is also required if you have had to remove Genie, explaining the reason why it had to be removed.

So if you need to remove Genie because she isn't working, you must FIRST ask her to leave. If she is still being a pain, then you can kick her, but first you MUST tell the others in the channel why you have to kick Genie off then channel. If you don't one of the other managers may think you are attempting to take over the channel and kick-an you off the channel also. However, you must NEVER kick, deop, or ban W, since that is the responsibility of CSC to deal with them problems.

You consider that person as a traitor to the channel, and instantly kick-ban them. They can explain afterwards why they were playing with the bots, however, even if it was a mistake they have probably cost the channel it registration, and I will be wanting to kill them.

When you consider the fact that TSA_list is a place where people can have a good time, without the problems of 'real-life', and if you look at the fact that both Zuul and I require the channel to be run like a fine hotel, with the same kind of respect for our customer, then one can understand why there is to be no fighting in public on the TSA_list channel.

Many times people can say they are having a open decision about topics, and most of the times this can not be classed as a fight. But, the same rules apply to the list as they do to a hotel. If the noise gets to loud, the people as asked to calm down, or leave. If they refuse to calm down (and talk in private about it) and they don't leave, then they are escorted to the door.

The rule is simple. No fighting on the channel, if there is and the people fighting do not stop when told to take it private, then the person who is continuing to fight is kicked off the channel telling not to come back until they cool down.

Well, this is a hard thing to list, because anything can be classed as fighting. However, I am not looking at making every disagreement a fight. I am however stating that if someone continues to disagree and it becomes a public all for one against the people involved, that this is stopped by the op(s) that are on the channel. Failure to stop this allows people to think we don't care, and then gets Zuul and I very upset when people comply about the fighting that is going on. To steal from the words of the TSA talk list, NO FLAMING IN PUBLIC. That includes formatting wars, operating wars, platform wars, anything that could be classed as a war online is not allowed. If you can't make the choice yourself, talk to the other op(s) on the channel and get backing if need be.

Another such fighting scene would be the fact some people on the channel seem to think it is in their rights to demand people do something, or act someway. They also demand the ideas of role-playing on the channel. Zuul and I have no problems with role-playing, as long as it is wanted by everyone. TSA_list is there to talk about mainly transformation and the likes, but it is not there to deal with a full blown role-playing game when only a few people are playing it. Ask the people nicely to take it elsewhere, as it will be effecting the normal running of the channel

Just remember however, not only do non-op'ed people cause fights or interact with fights. You op(s) must also follow this ruling. If you see a problem that requires you to fight it out with someone, take it off the list. If you can't and the person refuses to take it private, then kick them until they cool down, if they don't kick/ban them.

Also, please, make sure you don't call something a fight, just because you are not interested in the topic. Be careful in want you call a fight and what you don't. If it seems to be just a topic that people are talking about, then let them talk. But, if it gets to a stage where it starts drown out the other members of the channel, then take action, quickly and firmly if needed. We need to stop all this open fighting on the channel, before it becomes a cancer that we can not stop.

As stated above, your first course of action is to ask them nicely, on the main channel, to take the fight elsewhere. This allows everyone on the list to know you are taking action and that we will not stand by and allow this kind of behaviour to continue. If any one of them don't pay attention, again ask them with a firm warning that they will be kicked if they don't. This again must be done on the channel, because it will push home that we are not going to put up with the fighting on the channel.

If you are again ignored by any of the party, finally kick the person(s) ignoring you off the channel. Expect some flack from the people, telling you they feel like they are being treated unfairly, but you then tell them to complain to myself or Zuul, giving them my email address which I will forward on to Zuul. Then, if they refuse to do that, place them on ignore. (If you don't know how to do this with your program, find out, it is very very useful.)

If they come back into the channel, and continue to fight openly, then warn them again that this time you will kick and ban them off the channel. If they ignore you, do so.

I know this sounds harsh, but unless the rules of no fighting on the channel is followed, we will continue to have problems with people who think the channel is there for their own use and ignoring the wants and desires of the others on the channel. This we will stop, and make sure will stop. Don't be soft, be hard on this one if need be. This is our greatest problem as of now, and it is one that HAS to be stopped.

This is a problem that every channel suffers and continues to suffer as the years go on. Myself and Zuul have never wanted to keep a TOPIC line, so have never really told people not to talk about something. However, there are some off topic things that we will not allow on the channel.

They include:

Sex (And acting out sex on the channel)
Adult pictures, Kiddie Porn
Racists and nasty comments about difference
Spam Topics.
Advertising services, etc.
Being totally nasty to people
And anything that will cause in a war between people

This pretty much covers what topic's Zuul and I have always told people to leave off the channel, however, there may come a time where another topic turns up which doesn't seem right on the list. If you need to know if it should be on the list, email myself and it will come under vote within the Op(s) community.

Well, first of all nicely tell the person that the topic isn't talked about on the channel, and if they want to talk about it ask them to head to another channel. Again if they ignore, give them a final warning they will be kicked if they don't stop the topic. Then if they ignore again, kick them. Follow the same actions as 'Fighting on Channel' and this will allow the channel to continue to not have problems with off topic issues.

As stated above, if you ever have to kick someone, or kick/ban someone, always email the channel list explaining the situation and giving us the logs required. We are final say in all kick/bans and we are the people who will have to fast the CSERVICE people if there is a complaint. You failing to tell us about situations that could cause us problems, will only mean Zuul and I will not be able to protect the channels interests when needed to. Also, we will come down very hard on you, if you fail to follow up with this requirement.

The email list has been designed and maintained by DanielSan. The main reason for this list is a place in where all operators/managers/trainee's etc can keep informed about situations and choices that are made about the #TSA_list. Every person who is a member of the Management team MUST be on this Email List, if you are not on it - you are not one the management team, that simple. It is very important that ALL ops and management personal know what is going on, and what they should or shouldn't do about a situation.

Basically you go to this homepage address and follow the instructions on how to join the list. That will then send a confirmation to DanielSan who will then approve or decline your application to join. Don't worry however, if you are a member of the management team you will always be approved unless there is any very special situations regarding the email server itself.

The following section is a list of all the FAQ(s) (Frequently Asked Questions) files that are important for the running of #TSA_list channel. I have included all the important document files, even the manager FAQ, as I believe a knowledge operator/manager is better informed to make correct and intelligent choices.

History & Ethos of The Channel Service
======================================

Thanks to a lot of work by Seks and the rest of the Undernet IRCops, Undernet now has a channel service. This service will allow users to run a channel without running a bot. This service replaces the need for a bot on a channel.

This channel service gives the opportunity to users to manage a channel. This is *not* ownership because the service will only be placed on the channel if that there is a general demand for it. It cannot be used in channel wars/op wars or in an attempt to end "take over" a channel.

The Channel Service works the same way that a bot works. It can control all channel modes (including ops). One advantage that the service has is if ops are lost either due to someone messing up and deop'ing everyone (or a flooder/hacker doing it intentionally) then the bot can use Uworld (special Undernet service) and regain ops.

The Channel Service has many different modes. AlwaysOp will ensure that the bot always has ops. If ops are ever lost or the bot is unable to join the channel then the bot will use Uworld to gain access. NoOp mode will make it so the Channel Service is the only Op on the channel. All kicks, bans, topic, etc have to be made through the bot. Mode changes still need to be done manually. The bot also has flood protection against nick, kick, topic and mode changes to ensure that channel flooders are not a problem. Since both X and W are +d they do not monitor the discussion on the channel and will not monitor public message floods.

The Channel Service retains a userlist for every channel that it is registered on. The manager of the channel (person who registered the channel) controls the list for that particular channel. A reasonable level of traffic is required for the channel. Channels not having maintaining a reasonable level of traffic will be purged from X/W.

Please reference some of the Channel Service FAQ's at ftp.undernet.org in pub/irc/docs/cservice for general Cservice information. Please note that some of these documents may be out of date. If you have a specific question regarding the Channel Service mail Error! Bookmark not defined.cservice@undernet.org.

Structure of committee, and general aims
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Committee Procedure
~~~~~~~~~~~~~~~~~

Standard Registration:
~~~~~~~~~~~~~~~~~~

(i) Applications are reviewed on a regular basis by the CSC to ensure the proper information has been included.

(ii) Provided there is no objections the channel service will be moved into place on a trial basis, of 14 days. After which it will be permanent, subject to the standard review procedures.

Special Registrations:
~~~~~~~~~~~~~~~~~

Objections
~~~~~~~~

(ii) Any reasonable objection will be considered by the committee. The CSC shall attempt to invoke the following procedures:

(i) by trying to put them into contact with each other
(ii) by helping if requested to with discussions.

(c) if mediation fails, the BOT will NOT be placed on the Channel.

- a new application may be made in 2 months, but will not be considered before then.
- the committee will suggest that a channel under a different name be registered.

(iv) The decision of the CSC in all these matters is Final.

Involvement in Channels
~~~~~~~~~~~~~~~~~~~

(i) CSC administrators will only use their administrative access in order to perform channel maintenance, to enforce the CSC guidelines, and to aid channels in times of need.

(ii) CSC administrators can purge a channel if it is found to be used by abusive users, such as flooders etc.

(iii) Any CSC administrator/helper that abuses their access can have it suspended or removed without warning

IMPORTANT: Channel registrations are here to help established channels, not to start them. You should only be applying for a channel if you have a regular user base to the channel.

(i) Make sure that you have read these guidelines carefully, and are willing to use the channel service (X/W) in conjunction with the rules of use.

(ii) Applications are to be submitted via the Channel Service Registration page, found via the WWW (World Wide Web) at Error! Bookmark not defined.http://cservice.undernet.org/reg ist/ If you do not have access to the Web for some reason, please visit #cservice on the Undernet or mail Error! Bookmark not defined.cservice@undernet.org and a CSC administrator or helper should be able to help you.

a) The form is complete. Meaning, you have filled in every required section. The comments section is optional.
b) The user@host is formatted correctly.
c) The channel is not already registered.
d) There is no application for the channel already in posting stages.

If any of the above checks fail, the form is rejected, stating what parts of the form were incomplete or incorrect. You may then make whatever additions or changes are necessary and try to submit again.

(iv) If the application passes the initial checks, you will receive an "OPERATION SUCCESSFUL" message. A mail is also sent to the applicant and CC'd (carbon copied) to the supporters listed in the application stating that the application was accepted by the form processor.

(v) The email addresses in the list of supporters are checked for validity. If mail bounces back from one or more email addresses (ie, if any of the email addresses were invalid), the application will be rejected.

NOTE: Supporters are people that are regulars on the channel and feel that you would make a good channel manager for the channel. You should discuss the channel registration with them BEFORE applying. The applicant WILL NOT be notified via email if the application is rejected in this stage!! The applicant must check daily to see if the application has moved to PENDING or REJECTED.

(vi) Once the application has been accepted and passes the email address verification, it will be moved to the PENDING page and will enter its 10-day posting period. During this period, the application will be available for viewing via the web page. People will also be able to object to an application via the web page.

(vii) At the end of the 10-day posting period, the application will move into PENDING status. The CSC will at this point review the application and any objections posted.

(viii) Provided there are no valid objections, the Channel Service will be granted to the applicant on a trial basis of 14 days.

This trial period gives channel regulars, who may not have known about the pending registration, a chance to object to the registration. If an objection is received by the CSC for a channel which is still in the trial period, that objection will be investigated.

If the CSC finds that the channel was registered without the agreement of most of the channel regulars, it may be purged immediately.

After the trial period, if there are still no objections and no problems, the channel will be made permanent.

The Channel Service will not be responsible for any activity that occurs on the channel. Anything that occurs on the channel are the resposibilities of the people involved and has nothing to do with the Channel Service, its administrators and the Undernet as a whole, including the Operators that run it. The guidelines may change without notice.

- Original CSC Guidelines written by Super
- Amended by Super
- This Draft #Ox.1
- Amended by Teal and Super

2) Who are X and W?
X and W are the two Channel Service (CService) bots. They reside on Undernet's registered channels. Each registered channel has either X or W, but not both. They are exactly the same in the functions they can perform. The bots hold separate user lists for each channel they reside on. These are lists of users for each channel who have access to certain functions on the bots depending on the level and settings of the user.

3) What is a Channel Operator?
A Channel Operator (ChanOp) is a user who has been given the privilege of helping the Channel Manager run the channel. ChanOps are expected to abide by all of the Channel Manager's rules, as well as CService's rules.

4) What are the responsibilities of a ChanOp?
A ChanOp is responsible for helping to maintain the atmosphere that the Channel Manager has set for his/her channel. This means ensuring that all users abide by the set channel rules and warning/removing users who do not abide by them.

5) Who is the Channel Manager?
The Channel Manager is the person who registered the channel. There is generally only one Channel Manager, unless a special arrangement has been made with CService to have more than one. The Channel Manager makes the decisions on how the channel is to be run. This is the person to go to first if you have a problem on your channel.

6) Can a user be a ChanOp even if s/he is not on the user list?
Yes. A user can gain ops on a channel if they are given operator status from a current operator. This does not mean that just because someone makes you an op, you automatically have access to X/W. All it means is that you can pe rform any operator commands that you can normally do on a non-registered channel.

Line 1: nickname, user@host mask and access level
Line 2: channel name, autoop setting, protect setting
Line 3: how long ago user was last seen on the channel

8) How do I get added to a channel's user list?
Only ChanOps with ACCESS level 400 or higher can add users to the channel's user list. Who gets added is usually determined by the Channel Manager. Some channels may have a recommendation/voting process to add new ChanOps. Best bet is to ask someone who is a ChanOp on that channel.

9) What is this ACCESS level thing?
A user's level determines what commands the user has access to on X or W. Users will have access to the commands for their level, plus all commands for any levels below them. For example, a level 75 user will have access to ban a nd unban, plus the level 50 and level 0 commands.

• Level 500: set
• Level 450: addchan join part remchan
• Level 400: adduser clearmode modinfo remuser status
• Level 100: deop invite op suspend unsuspend
• Level 75: ban unban
• Level 50: kick topic
• Level 0: access banlist chaninfo deauth help lbanlist map motd newpass pass showcommands showignore verify

• 500 Channel Manager.
• 450 & 400 Trusted Administrators. These are ChanOps that the Channel Manager has allowed to help in administrative duties on the channel.
• 100 These ChanOps can command X to perform all regular ChanOp commands, including some special X/W commands.
• 75 & 50 These ChanOps can command X to perform most regular ChanOp commands (see above list) as well as some special ones.
• 0 All users who are not on the bot's user list for that channel. Also, any ChanOp who has a password set, but has not yet msg'd the bot with his/her password will be seen as a level 0 user.

11) What is AUTOOP?
When AUTOOP is set to ON, you will be automatically opped by X upon entering the channel. If you have a password set though, then AUTOOP will only work if you /msg X with your password BEFORE you enter the channel.

13) Why would I use a password and how do I set one?
A password gives more protection against someone faking your user@host and obtaining ops. If you have a password set, X/W will only recognize you if you have the correct user@host AND give the correct password.

14) What happens if I can't remember my password?

Your password will have to be reset by any 400 or higher level ChanOp on your channel. Speak to one of them. You can find out who these are by:

/msg x access #channel -min 400
or
/msg x chaninfo #channel (tells you who the channel manager is)

17) What exactly does CService consider abuse?
Any time X or W is kicked, banned and/or deopped, this is considered abuse of the Channel Service. The CService bots are not to be played with. So-called "testing" of the bots is not allowed. Abusing the Channel Service could result in you losing your ops or even being banned from the channel. The channel could also be placed in NoOp mode or even purged if necessary to prevent further abuse.

18) What is NoOp mode?
NoOp mode means that no one except X will be able to have ops on the channel and all kicks/bans must be done through X. Here is where the access level really determines what commands a user can perform.

19) Where can I get more information about X/W and CService?
Online, you can '/msg x help' for help with commands. You can also obtain help from someone in #cservice or any of the CService Admins who happen to be online. If you can't find someone online to help, you can email cservice@unde rnet.org and someone will respond via email. Also, all CService documents can be obtained from ftp://ftp.undernet.org/pub/irc/docs/cservice/

20) Who are the Channel Service Administrators?
The Channel Service Administrators are users who have administrative access to the Channel Service bots. The CService Admins are volunteers who are committed to making sure the Channel Service is used as it was created to and that the Channel Service is not abused. CService Admins represent the Undernet Channel Service, as well as the Undernet as a whole.

This file answers some of the most frequently asked questions regarding the Undernet Channel Service and the X and W bots. If your question is not answered here, check the sources found in Section 5. If there is a question that you feel should be in here, send it to Error! Bookmark not defined.Signe@alias.undernet.org.

The Undernet Channel Service (UCS), aka the Channel Service Committee (CSC), is the Undernet committee responsible for the registration of channels and for handling problems with those channels. It is comprised of unpaid volunteers who want to help out.

The CSC is not owned by any one person. It is an organization chartered by the Undernet administrators, and run by the CSC administrators (see Error! Bookmark not defined.1.7). Currently Marylee McCleary, aka merri, oversees the CSC.

The CSC does not have a physical office or phone number. Some helpers and admins can be found in channel #cservice on Undernet. All correspondances should be emailed to cservice@undernet.org

The CSC relies solely on the donation of time, disk space, and services by Undernet administrators. The CSC helpers and admins are not paid for their time. The disk space and computer time to run X/W are donated by the respective system administrators. The CSC does not charge for channel registrations, and therefore does not turn a profit.

Generally, CSC helpers are people who hang around on #cservice and help out answering questions. Trusted helpers are those who have been around for a while, and are trusted by the admins. CSC admins are chosen by the current administrators, usually from the trusted helpers. If you want to help out, just join #cservice and start answering questions.

Trusted helpers and admins can be verified through X/W with one of the following commands:

/msg X verify nickname
/msg W verify nickname

Sometimes helpers may not be verifiable by this method. You should then ask #cservice if they are truly a helper. If you have the slightest doubt about someone's claim to be a helper or admin, do not hesitate to check it out. If you find that someone is impersonating a CSC admin, please report it to #cservice.

Currently, the list of CSC admins is as follows: Super, Seks, Kev, cowboy, meredith, Morrissey, Chaos, Teal, jini, Jase, Signe, AnElf, Pucker, BitBT, TerraByte, NudeDude, Manning, D-In-TX, Crip, and MatthewA

X and W are the CSC bots, written by Seks. One of these is assigned to each registered channel. For each channel, these bots maintain a userlist, which specifies who has what access and who should be opped, and a banlist, which specifies who to ban from joining the channel (or from getting ops), and for how long. They are designed to keep a channel open 24 hours a day, and prevent channel takeovers.

X and W are actually each servers, not just bots. They are allowed to work this way because they are run by the Undernet administration. This allows them to do several special functions, such as regaining ops if ops are lost. Also, each bot is on a large number of channels. By having one bot for many channels, this reduces the load on the Undernet network that would be caused by having one separate bot on each channel.

There is no difference between X and W as far as the commands and services availible is concerned. The only differences are that X and W each run on separate computer systems and networks, and each one handles a different list of channels. The bots are assigned to registered channels at random.

Just like any other bot or user on Undernet, X and W are subject to lag and netsplits caused by bad connections between Undernet servers. This can cause X and W to slow down drastically (sometimes up to 5 minutes lag), and even disappear. If this happens, please be patient. Be assured that Undernet and CSC admins are working to get them back to normal as quickly as possible in the event of a problem.

X and W each require a lot of disk space and computer resources. And on top of this, they need to be run on a machine that is an Undernet server. Currently, the system administrators of irc.direct.ca (vancouver.bc.ca.undernet.org) and irc.wildstar.net (okc.ok.us.undernet.org) are donating the neccessary resources. While it is possible to move X and W, it is not feasible, as there is not another system to move one of them to right now, and moving them involves a lot of time and work.

Registration not only provides you with the ability to keep your channel open 24 hours a day, it also gives the channel stability. In the case of a channel takeover, the manager always has ultimate control to regain the channel. Also, it provides you with a way to have users auto-op'd, and a more permanent banlist.

Almost any Undernet channel can be registered. The only types of channels that are currently excluded are

• warez-type channels
• channels dealing with child pornography
• channels dealing with hacking/abusing IRC (including flooding)

The CSC admins do reserve the right to reject any channel registration for any reason that they deem valid. Do not try to change the name of one of these types of channels, or try and conceal the channel activity, as CSC has many ways of finding out the true uses of a channel.

To get X/W onto your channel, the channel must be registered. In order to do this, you must first have some consensus on the channel as to who will be the channel manager. Then you must have 10 supporters. Supporters are people who frequent your channel (not neccessarily ops), and want you to register it. Once you have these two things, you need to fill out the Error! Bookmark not defined.registration form, which can be found at the CService WWW site.

Supporters are required because the CSC only registers established, well used channels. By requiring supporters, CSC can know that there are at least 10 people who use this channel. It also prevents users with malicious intents from taking over a channel by registering it out from under the true users of the channel.

The CSC frowns greatly on multiple channel managers. This is because in the case of a dispute between channel managers, there is no way for CSC to mediate. Multiple managers are only allowed in extreme circumstances, and to have more than one manager you must petition cservice@undernet.org with the reasons.

After your registration form is received by the CSC, the supporter email addresses are checked and each supporter is mailed a copy of the application. The applications is then posted to the Error! Bookmark not defined.regisistration WWW pages under new applications. They are left in this category for 10 days, during which time other people can object to the channel by using the web pages. The application then moves to the "Pending" section. Here, the applications are also reviewed by CSC to make sure they meet the criteria for registration. If the applications is approved, you will receive an approval email and a copy of the channel manager's FAQ. The channel is added as soon as it is approved. The entire registration process takes 3-4 weeks to complete.

Every week, there are many registrations to be processed. Some weeks there are over 250 applications. Each of these applications must be checked for completeness, checked to see if it is already registered, and then compiled into the pre-registration list. Then the posting period must pass, objections must be evaluated, and a final registration list compiled. All of this work is done by one CSC admin, who is a volunteer who has other things to do, such as work or school. After this final list is compiled, it must be reviewed by the admins, and then they must make time to add all the channels, which is a time consuming task. This is why the registration process takes so long.

You can check to see if your channel has been added to X or W by typing the following commands to check both bots:

If you do not hear anything from CSC, one of several things may have happened:

If 5 weeks have passed, check the Error! Bookmark not defined.registration pages and make sure your channel was not rejected. Also check the "New", "Pending" and "Accepted" categories. If your channel is listed, be assured that CSC is processing it. If your channel is not listed anywhere, resubmit your application.

Because your channel is not technically a registered channel until it is actually added to X or W, there is nothing that CSC or #cservice can do to help you with channel problems at this point. You need to talk to an IRCOp, which you can find on #wasteland, and ask them if they will help you out.

Congratulations, you are now a channel manager. The channel manager's FAQ, which you will have received by email before now, will tell you how to set up the channel and userlist. Please read the manager's FAQ thoroughly.

Each user is allowed to register one channel. They may, in addition to this channel, register a help channel that provides assistance to users for things such as: Software products, Internet services, Internet Service Providers. If you are unsure if you channel falls under this category, email cservice@undernet.org and ask. ("Each user" is defined as a person, not as an email address. If you have multiple email addresses, you may not register multiple channels. One channel, and optionally one help channel, per person)

Since the registration is for the channel, there is no provision for changing channel names. If you wish to do this, you must fill out a new application for the new channel and submit it, following the normal registration process. In the comments field of your application, write a note saying that your are the channel manager of #youroldchannel and would like to have it purged from the registered channels list in order to register a different channel.

If you think you have a valid reason why X/W should not be on a registered channel (see Error! Bookmark not defined.4.2), such as the manager is never around, or it is a warez or child pornography channel, you can email your complaint to Error! Bookmark not defined.cservice@undernet.org. If there is a lot of support for your complaint, please include the email addresses and nicks of those who support you in your letter (do NOT have everyone send a separate letter). The CSC admins will evaluate your complaint, and if it is valid, action will be taken.

Because CSC does not consider content during the registration process, excepting warez and child porn channels, there is nothing you can do about this. The CSC specifically disclaims responsibility for the content of a channel, and the way the manager chooses to run the channel, as it would be an overwhelming task for CSC to police every registered channel.

As stated in 4.2 above, the CSC has no reponsibility for, nor say over how a manager, and those he gives operator status to, choose to run the channel. A channel operator can kick and/or ban someone for any reason they choose, or no reason at all. Therefore there is noone taht you can complain to about this except the people who run that specific channel (the manager).

Because X and W are Undernet services that exist to provide stability to registered channels, the Undernet and CSC admins have chosen to modify the Undernet servers to make it so that X and W cannot be kicked or deopped. By doing this, the stability of registered channels is greatly increased, and the load on the Undernet IRC network is decreased. This modification is in effect on all Undernet servers at this point in time.

If you think an admin or helper was unnecessarily rude or abusive towards you, please make sure you have a log of the incident. Email this log, and a note explaining the situation, to cservice@undernet.org. The admins will read and evaluate the situation, and respond accordingly.

The CSC maintains a help channel on Undernet called #cservice. There are helpers and/or admins on this channel almost all the time. However, please make sure you have checked this FAQ, and the Op FAQ before asking a question there. If there is noone there to answer your question, you can email it to Error! Bookmark not defined.cservice@undernet.org.

The manager's FAQ is availible several ways:

The Op FAQ is availible several ways:

CSC maintains a single consolidated web page. On these pages, in addition to getting information about CSC and X/W, you can access channel userlists, banlists, chaninfo, and perform whois and channel searches on Undernet. The pages are located at:

• Main Page -- Error! Bookmark not defined.http://cservice.undernet.org
• Registration -- Error! Bookmark not defined.http://cservice.undernet.org/regist

If none of these methods work, and you still have questions, feel free to email them to Error! Bookmark not defined.cservice@undernet.org

This FAQ was composed by Todd Palino (Signe). Some of the questions were gathered from the original Xfaq.general.

All comments, quips, quotes, and additions should be sent to Error! Bookmark not defined.Signe@alias.undernet.org

Introduction: This FAQ is to answer general questions that channel managers may have in regards to the Undernet Channel Service (UCS). If you don't know what the UCS is you should get the Undernet Channel Service FAQ from ftp.undernet.org in /pub/irc/docs/cservice. In all examples, we will assume that the channel name is #foo, the nick is foobar, the user@host is foo@test.com.For ease of documentation, X will be used in all examples, but there are 2 channel service bots, X and W.

The confirmation letter means you have been added as the channel manager of the channel that you applied for. If you are anxious and/or having mail problems you can check if your channel has been added by doing a /msg x,w chaninfo #channel. This will return a response from both channel service bots to say whether your channel has been registered or not. Your channel will only be registered on one of the two bots.

As the channel manager, you are responsible for all activities of your channel including its users and bots. It is recommended that you do not run other bots on the channel besides X since there is no need for it. X will always be there and maintains an oplist. You are also responsible to ensure that none of your channel operators (including bots) are not running hack protection scripts (such as phoenix). You are also to ensure that none of your ops deop/kick/ban X. This is considered abuse and will be dealt with severly and can result in the removal of X from the channel. "Testing", such as seeing what will happen if X is deop'd, is considered abuse.

The Channel Service Committee has added the IRC address that you specified in your application form to the UCS bot X. To check the user@host that has been added you can type /msg X access #channel nick. For example: /msg X access #foo foobar. If your user@host is not correct contact the CSC by sending mail to cservice@undernet.org or drop by #cservice and ask.

To find out what commands you have access to do a /msg X showcommands #channel. It is also a good idea to have a password, just in case someone is using a hacked username and is able to replicate your user@host name.

Most users with PPP/SLIP access from your site or sites that do not run identd can have hacked user@host. This means, the user can select the userid of their choice at any time they wish. In general it is a good idea to have a password. To setyour password type /msg X newpass password. For example to make Foobar's password into FooPass1 it would be /msg X newpass FooPass1.

If you have a password set, X will not recognize you until you send X your password (even if you have AutoOp set on. You can identify yourself to X using /msg X pass #channel password. For example: /msg X pass #foo FooPass1X will return a confirmation message to say that your identification iscorrect. If you have lost or forgotten your password, contact the CSC and askthem to reset it for you. Once you have identified yourself once, you should not have to do it until you log off of IRC. In some instances of netsplits and the rare occurance that X needs to be restarted, you will need to resend your password.

First thing you will want to do is move X onto your channel by sending X a join message /msg X join #channel. For example: /msg X join #foobar. To have X leave your channel do a /msg X part #channel. This will not remove you from the channel service, it will just move X off of the channel. You can bring X back at any time by sending the join message. Now you will want to add your channel to X by /msg X addchan #channel. For example: /msg X addchan #foobar. This will add #foobar to the list of channels. This will add your channel to the channel database for X which must be done before anything else.Also this will set up all of the channel's defaults.

The channel defaults are X modes such as flood protection level, AlwaysOp, NoOp, etc... To see what the X settings are for your channel type /msg X status #channel.

When X is on the channel you can now configure X for the channel. The variables the can be set are: MassDeop, NickFlood, FloodPro, NoOp, and AlwaysOp.

MassDeop is the maximum number of deops one user can do in a 15 second period. This is an integer value and is set by /msg X set #channel MassDeop #. For example: /msg X #foo MassDeop 5. NickFlood is the maximum number of nick changes one user can do in a 15 second period. This is an integer value and is set by /msg X set #channel NickFlood #. For example /msg set #foo NickFlood 5. FloodPro is the limit of TOPIC, MODE, and KICKS that one can send to a channel in a 15 secondperiod. This does not cover public floods since X is deaf to all public messages to the channel. This is an integer value set by /msg X set #channel FloodPro #. For example: /msg X #foo Floodpro 20. Any user surpassing the set levels will be kicked or deop'd by X.

NoOp is a special mode where X is the only channel operator. This is an on/off value that can be set by /msg X set #channel NoOp on/off. AlwaysOp is a mode that ensures that X will always be an operator. This canbe set with a /msg X set #channel AlwaysOp on/off. The default for NoOp is Off and AlwaysOp is On. If a user with access >= 450 deops X, AlwaysOp is turned off automatically. If a user with access >= 450 kicks X, AlwaysOp is turned off AND a remchan is issued, so X won't rejoin. NoOp mode can only be reset by the channel manager.

To add a user to X's oplist you must be at least a 400 level operator on the channel. If you have the correct access, you can addsomeone by /msg X adduser #channel nick *!*user@host level password.The pasword and user@host fields are optional and you may only add someone to a lower level than you are. For example, if I am foobar with level 500 (channel manager) and I want to add foo2 who's irc address is foo2@my.own.server with a password of foopass I would /msg X adduser #foo foo2 *!*foo2@*.own.server 400 foopass By placing an extra * in the host name creates a larger host mask that will cover differnet server names that the user may have. However a *!*@* would be a really bad entry since that covers all users. Be very careful with your use of the * on the userlist.If there are entries that pose a threat to X it is considered abuse and will be removed and can result in the complete removal of X from the channel. If the user is on Undernet at the time that you are adding them, X will automatically add the wildcards to the user@host if a /msg X adduser #foo nick level format is used.

When adding someone you can give any level you wish as long as it is less than your own and it is a positive integer value. However, a user must have a certain level to gain certain access. Level 500 - Channel Manager
>=450 - Trusted Admins (can remove X from the channel)
>=400 - List administrator, may add users to the userlist
>=100 - Channel Operator

The user list for the channel can be received by/msg X access #channel * the asterix will show all users that have access on the specified channel. If you want to check a specific users access type /msg X access #channel nick.

You can give someone autoops on the channel by adding them to the user list at any level (that is less than yours) and using the modinfo command. /msg X modinfo #channelname AUTOOP nick ON This should get the channel service bot to respond and show you the person's entry in the database reflecting the change. This also applies to PROTECT.

In general, there should only be one 500 level user. In some extreme cases the CSC will allow a second channel manager. If there was more than one 500 level user there can be disputes with the 500 level users which will lead to problems since all 500 level users have the same access. It is best to choose one person to be the channel manager and have that person add the others at level 499. The only command that the level 500 person has is the set command which is rarely used.

One of three things may be occuring. You may have had your access suspended. Your access can be suspended for deop'ing X, attempting to op someone that is not allowed to be op'd (banned or suspended user), banning/kicking X, etc... To see if you have been suspended type /msg x access #channel mynick Your user@host may also be different. Just /msg x access #channel mynick to check if your access is correct. Thirdly, you may need to send X your password if you have one set. If you still cannot get X to respond, contact the Channel Service Committee.

If there is abuse of X and a CSC representative is available, they will join the channel and warn the users and answer any questions they might have. If the abuse problem is severe (repeated deop's of X), then the channel will be placed in NoOp mode and the channel topic will be changed to reflect this. Only the channel manager can reset this mode. If you find the channel you manage in NoOp mode, you can assume that there was abuse. This is also a warning for the channel manager to ensure that their users will not abuse X in the future.

No. These are the basics. There are a lot of things in here but there is still a lot to learn. Managing a channel is not an easy task. Managing a popular channel is even harder. If you are unsure, please ask.