The Guide to #AHotTub

Charlie Robinson

Welcome to the Tub

This Guide is designed to help you better understand what our channel is all about. Your comments and suggestions for improvement will help this guide get better over time. I can be reached at:

cjrobi@icon-stl.net.

For those of you who have been in the channel for a while, a lot of this may seem redundant, but read it anyway -- there are things here I haven't had time to explain online, some resources on the Web, and maybe a surprise or two along the way.

#AHotTub is an adult-oriented channel on the ChatNet IRC network. Unlike many channels, which have a topic or theme around which they are organized, #AHotTub has a physical metaphor, the hot tub and its surrounding space. It is intended to be a place for adults to gather, meet other adults, chat, joke, relax and maybe flirt a little if they're so inclined. As I've often said in response to the inevitable question, the topic in the Tub is life, love, laughter and liquor -- not necessarily in that order. The objective of the Tub is to provide a refuge from any of the aggravations so common on IRC. The channel operators try to limit the intrusions by hormonal teenagers who burst into the conversation with requests for age/sex checks or inquiries as to the bra size of every female in the channel. Those who are looking for that sort of entertainment are encouraged to visit channels like #Cybersex, preferably on another network.

This is not intended to imply that the Tub is run by the Disney folks. The language and the topics discussed in the channel are not always suitable for your eight-year-old, but we are not operating a porn trading channel, a cybersex service, or a haven for pedophiles. We simply want a place where we and people like us can get away from some of the annoyances that are all too common on much of IRC and spend some relaxed hours in a congenial atmosphere.

I've had the opportunity to observe other channels and seen some of them come and go without a whimper, while others become successful initially only to fall apart because of internal factionalization and feuding. I don't want to clamp down on the Tub -- the free-wheeling nature of the conversation is exactly what makes it so special. All I'm trying to do in this Guide is help us establish common ground and let you know how #AHotTub came to be and share my goals for the Tub. I'm also asking for your input. Let me know what we can do to make the tub a better place for you.

A Short History of #AHotTub

I first met Judi in the Hottub room on AOL in the fall of 1995. When we moved to IRC full time, we spent some time in channels that other people had founded on EFNet, visiting with friends from AOL as well as with people we'd met on IRC. When we would open a channel for people to come see us, it was usually a hot tub, because it was a metaphor we were both comfortable with and it seemed to attract people we enjoyed talking to. Our first "permanent" channel was #AHotTub on DALNet, where Chanserv made it easy to establish a channel. It was called #AHotTub because it seemed every net already had a channel called #Hottub, and it put us higher in the channel list -- we got more visitors. Unfortunately, DALNet quickly outgrew its capabilities. Lag and splits grew increasingly annoying. Also, the prevalence of cybersex and porn channels on DALNet made it as HNG-infested as the older nets. When NewNet was started, we moved there and again registered the name #AHotTub. It wasn't long, though, before NewNet began to be plagued by lag and netsplits like all the others. On NewNet, as on EFNet and DALNet before it, we had a small core of regulars, but it was always a quiet channel with only an occasional busy night.

I honestly don't remember which of us stumbled across ChatNet when it was still very new -- probably Judi. In any case, we looked it over and decided it would be a good next place for a channel. Checking into the ChatNet home page, I found out we would need to fill out an application and get the email addresses of five people in addition to myself who supported the channel. Judi and I talked to some friends from a channel based on EFNet that was going through a process of disintegration and got four of them to "co-sign" the channel application. In the first couple of days, before we even had the bot in the channel, we'd already gathered a few new regulars into the fold. That was last October. As of this writing, we've had over 40,000 joins recorded in the channel. It's not unusual to pop into the channel in the evening and find twenty or thirty people there.

Physical Layout of the Tub Space

Because our shared experience revolves around a virtual space, rather than a topic, you might want to know how I visualize the Tub space. That way, we're all talking about the same thing and we're much less likely to get lost. The Layout page gives you a rough sketch of the Tub layout. As you enter the channel, the Tub is directly ahead of you. Around the hot tub to the right is the bar and beyond it the locker room and restrooms. In the corners of the room are couches and chairs forming conversation areas. At the rear of the space is the door to the private beach and the "back room". Please also make note of the hammock set up near the tub for the channel owner's use.

Speaking of the bar -- and most visitors do, sooner or later -- it's very well stocked. We don't have a bartender, though, so it's self-serve. I don't really want to maintain a bartender bot, nor does ChatNet encourage bots on the network other than K9. When the Tub was smaller we had a rule that the youngest person in the channel tended bar, but that's not really practical anymore.

The Tub space has a deep, plush carpet everywhere but the hot tub itself, its surrounding apron, and the restrooms. Those areas all have ceramic tile. The lighting is soft and indirect, flattering to the ladies but bright enough that no one should be fumbling around unable to see. The bar area is easily accessible to the hot tub and conversation areas.

The Tub has computerized controls that maintain optimum temperature and water circulation. I consider it rude when a non-member takes it upon him/herself to adjust the Tub controls. I wouldn't mess with their stuff, so I don't think they should fool around with ours. (The same is true for the channel topic. If K9 is down, the topic is unlocked. That doesn't mean that any yahoo who wanders in off the street has the right to alter the topic. If they do, call them on it. If someone's back door is unlocked does that give them the right to walk in and write a note on their refrigerator?)

#AHotTub Etiquette

Now that we have a shared map of the "space" we occupy, let's talk about what we do there -- and what we don't do. The Tub is "clothing optional". Visitors are invited to leave their clothes in the locker room, but if anyone resists this virtual nudity, that's their choice. The same is true of the bar and the tub itself. No one will be forced into anything

I've already mentioned age/sex checks as a pet peeve. They are symptomatic of a class of users I call HNG's when I'm being polite. Horny net geeks come in both sexes. Some even pretend to be a different sex, presumably because they can't get cybered as themselves. They have a right to pursue happiness on IRC, but not in this channel. You may have seen me call somebody on "trolling" in the channel. Trolling is advertising for cyber, anything from "Who wants to get it on?" to "Hot 21/M - msg me!" We aren't attempting to ban netsex (heaven forbid!), we just prefer that those who seek it do so one-on-one and that they not harass other users if they don't get what they want.

Picture trading is also permitted, as a means for members to get to know one another better. We don't care if you want to give away R or even X rated pictures of yourself, just don't hawk them in the open channel like a street vendor or offer pictures purporting to be of your significant other, commercial or amateur porn, or child pornography of any sort or you will be kicked from the channel. Female members wondering if their pictures are acceptable are free to submit them to the channel owner for consideration <grin>. I'm sure that Judi, JournyGrl or one of the other Tub ladies would be willing to offer similar screening for the men. Seriously, we're not trying to keep people from trading personal pictures, just following ChatNet's policy of not allowing porn servers.

We don't allow harassment of other members. The basic rule of the Tub is "Play nice." Annoying or abusive visitors should be placed on ignore if possible, rather than being kicked. I've learned from experience that most of these pests are simply seeking attention and that ignoring them is more frustrating to them than the negative attention of a kick. In fact, if you want a good giggle, don't put some dork on ignore when everyone else does and watch his frustration as he realizes no one even sees the garbage he's spewing out. This isn't always possible or desirable, especially in the case of flooders or takeover artists. Before placing a kick on someone, we prefer a background poll of the other ops present using PIRCH's /OPNOTICE command (more on this later), except in emergencies. If a single kick serves to cure someone's attitude problem, fine. If they return to the channel and continue their undesirable behavior, try a ban through K9, being sure to specify a time and adding a comment to the ban so we know what it's for. In the case of minor pests, try a five-minute ban. This is long enough that most of these characters will go off looking for another channel to bother rather than waiting for the ban to expire.

In general, my philosophy is to do online what you'd do in real life. Would you walk into the corner tavern, tell everyone how big your equipment is and ask every woman in the place if they want to screw? If you did, would you get a punch in the mouth? Why expect anything different online? It applies to both sexes, though when a female nick appears in the channel claiming 38DD boobs and asking for the hot guys, my first reaction is to do a whois on the assumption that it's a guy who wasn't having any luck with the "any hot chicks wanna cyber?" approach. In one case, I replied to such a user with "Why would you want to know that Paul?" The idiot actually asked how I knew his real name and seemed more insulted than embarrassed when I told him it was in his whois. I really was rolling on the floor laughing over that one!

Popups and Waves

As a group, the Tubbers seem to be both popup-happy and wave-happy. I have no problem with this; I'm as crazy as the rest of you. Please try to bear in mind, though, that when the Tub is crowded a lot of large popups going off at once can constitute flooding, in that they make it difficult for everyone else to talk. Try to limit large multiline popups to less active periods or at least warn people when you're about to trigger one. If someone is going to run a large popup, especially an image, please avoid typing till it's done so that it isn't chopped up. The same holds true for waves. I know that I have PIRCH configured so that an incoming wave replaces one currently playing, so if a new wave is triggered before the current one finishes, I lose it. Some people have the opposite setup, so they won't hear your wave if another one is playing. Try not to flood the channel with waves, though I know that sometimes it's hard to gauge, particularly if you don't have the wave that's playing. We encourage everyone to share their popups and wave files, but we also like to acknowledge creativity. If you know the author of a popup, a little note to that effect is appreciated. I use the copyright symbol, © [Alt+0169], on my own popups and those that I steal if I want to acknowledge the creator. Removing such notices when you "borrow" someone's original popup makes it look as though you're trying to claim authorship yourself. I propose that the "citation for popup theft" popup not be used as long as someone acknowledges authorship, but encourage its use in those cases where someone implies original authorship by removing those notices.

Kicks and Bans

I would hope that we could all have fun in the Tub without the need for kicks or bans, but this isn't always the case. On the other hand, newcomers to the Tub who see too many people getting kicked may well decide that this is not the place for them. Kicks should only be done by consensus, except in emergency. In the case of a personal attack on one of the ops, that op has the privilege of doing the kick -- so wait your turn, it'll come. I won't kick someone because of the other channels they're in, as long as they aren't in kiddy porn or abusive channels. Just because someone's in #Cybersex doesn't rate a kick; too many of our own members spend a significant amount of their time in the back rooms. If they're logged into #KiddieSex, #Rapesex, #KidSexPics or the like that's a different story. The same is true of the neo-Nazi who came into the channel a while back...I banned him until the year 2011.

Essentially, the following list contains the reasons I see for kicks and bans, though most of these aren't automatic. I do think ignore should be used first, except in those cases marked with a +.

Membership in the Channel and Channel Operator Status

ChatNet uses a database, accessible through K9, to keep track of which users are registered members of a channel. Membership gives the user access to the network bot, K9, in the channel. The K9 FAQ file on the ChatNet Channel Service page at http://cservice.chatnet.org lists the commands available and the user levels required to access them. Our policy in #AHotTub [effective 5/15/97] is to set up all new members with user level 75, which gives them sufficient access if they are granted ops to use all the commands they will need. Regular ops will have user level 200. A few users have level 400 or higher access, allowing them to modify the user list. The channel owner is the only one that ChatNet allows to have level 500. ChatNet Channel Services staff and the ChatNet IRC operators (IRCops) have level 600 access to K9 in all the channels.

Membership in the channel doesn't automatically equate to having ops. We invite regular visitors to the Tub to become members in order to show them that we like having them in the channel and to encourage them to spend more of their online time with us. Every member is encouraged to let the channel owner or designated operators know if there is a user who is visiting the Tub on a regular basis and seems to be the kind of person we want to invite into membership. Channel membership carries no obligation except to conform to the Tub norms and to contribute to the conversation. No one will be drafted into membership. Before being added to the user list, potential members will be asked if they approve and should be furnished with a copy of this Guide.

We will post the names of candidates for membership on the Membership page of the web site. All members are encouraged to check the site each week between Sunday and Friday and register their votes either by leaving a private message on the guest book or by sending me an email message. Soon we hope to have a form on the site that you can use for voting.

Members are asked to provide the channel owner with some personal information to help in the administration of the channel. Please let us know any alternate nicks you use frequently, whether you use alternate providers (so that we can set up K9 to recognize you when you come in the channel), your e-mail address (so we can send you information about the Tub), and (optionally) your real name and location, as well as any other information you want to share with the other members (e.g., your spouse's nick). All of this data will be compiled into a member directory which will be e-mailed to all the members on a regular basis. Please let us know if you don't want your e-mail address or other information to be published. We also encourage you to set up your user bio record if you're a PIRCH user, and to include code in your Events section to allow other users to retrieve your bio. When you are added to the user list, you will need to select a password and provide it to K9. On future visits, use the AUTH command to tell K9 who you are and enable your access to the K9 commands.

Channel operators are users who have access to commands that help maintain the channel and protect other users from harassment. In other words, they can kick and/or ban users from the channel. They also have access to the channel topic, which is ordinarily restricted to prevent HNG's from flying through the channel and changing the topic for their own amusement. After being added to the user list, members may have the Auto-op switch set on in their user record, which will cause them to be opped whenever they join the channel. Ops have been granted in the past on the basis of seniority -- if you hung around long enough, you got ops. We now have enough ops to keep the channel running, and in the future we'll be extending operator privileges based on merit. That is, we will be looking for people who show maturity, judgment and technical competence with their IRC client software and in using available K9 commands. Ops have a responsibility to the other users in the channel to help make their time in #AHotTub enjoyable and free from harassment. Ops do not have an obligation to train users in the use of their IRC client software or teach them how to write popups. If an operator does so, it is entirely at his or her discretion and implies no future obligation. If the Tub is busy, feel free to refer the user to the #Pirch_101 or #K9_101 channels as appropriate.

All Operators Please Note:

All granting of operator privileges, temporary or automatic, must be approved by one or more of the 400-level operators and/or the channel owner. The only exception to this is in the event of an emergency (e.g., takeover attempt) when the ops currently in the channel grant ops to a visitor known to them to be technically competent to help with the emergency. The reason for this policy is to stop the practice by some ops of granting ops to non-members of the channel for reasons of their own. This is not acceptable, and it places the outsider in a very uncomfortable position, as they will be de-opped and quite possible kicked from the channel. Any op granting operator privilege in this way will also be de-opped and their operator status suspended.

If someone known to you to have operator privilege joins the channel and K9 does not op them in a reasonable amount of time and none of the 400-level operators is present, check their access (/MSG K9 ACCESS #AHOTTUB <nick>) and if K9 reports that they have no access (probably a mask problem), then go ahead and op them. Also, if K9 is non-operational, go ahead and grant ops to regular operators joining the channel.

On the subject of overwhelming visitors with the number of ops in the channel, remember that you can deop yourself at any time. If you're a Level 200 or higher member, you can op yourself once again via K9 or you can ask someone to reop you if you want the @ back. Don't ever feel you have to deop yourself because someone make a smartass comment about the number of ops, but feel free to do so if you think it will make a potential regular feel more comfortable.

Why Am I Not An Op?

It is important to note that not being granted operator privileges does not mean you aren't valuable to the channel. If we felt that, we wouldn't have asked you to become a member. It simply means that we don't have a need for more ops at the time (we'd like to avoid having more ops than regular users in the channel most of the time). Or perhaps it means that you need to refine your skills with PIRCH or mIRC and/or your ability to make use of K9. If you feel strongly that you or someone else should have operator privileges, e-mail cjrobi@icon-stl.net and let me know. I'll be happy to discuss the situation with you. The same is true for any concerns or ideas you may have for making #AHotTub a better place. I am always open to suggestions; my objective is to make the Tub the best channel of its kind on IRC.

Channel Operator Communications

Most of the members in #AHotTub, especially the ops, use the IRC client PIRCH. All other issues aside in the PIRCH vs. mIRC debate, PIRCH supports the OPNOTICE command, which makes it easy for the ops to chat among themselves in private. The syntax for this command is:

/OPNOTICE #<channel> <message>

If you want to make it easier to use, create an alias in PIRCH. I call mine OPS and it's defined as /opnotice # *1, which allows me to use it in any channel where I have ops.

[5/6/97] mIRC version 5.2 now supports equivalent commands, though the opnotices don't appear in my channel window for some reason; they instead appear in a message window like any private message. The following extract is from the mIRC 5.2 (32-bit) help file:

/omsg [#channel] <message>

This and the /onotice command sends the specified message to all channel ops on a channel. You must be a channel operator to use these commands. If the #channel isn't specified, then the current channel is used.

If you note that a particular user is a consistent source of trouble, please e-mail the other ops and let them know. If the ops know that the person currently causing a disturbance is a constant troublemaker, they can skip the initial gentle treatment and go straight to a ban.

Online Help Requests

The main reason I come to IRC and to the Tub in particular is to have fun. I'm here to visit with Judi and the rest of the Tubbers. Unfortunately, sometimes I get so many private chat windows going from people who want advice or help that I lose track of what's going on in the channel. I like to help people, but it gets out of hand. What I'm asking is that requests for explanations of K9, IRC or PIRCH commands, discussions of channel policy, etc. be handled via email whenever possible or held for times when the channel is idle.

The #BackRoom Channel

When several ops need to have an extended discussion, it may be more convenient to use the channel #BackRoom. This channel is not registered with ChatNet, so it may not be available at any given time, but we have never had a problem in the past. If you want to call an operator meeting, open #BackRoom, make it invite-only, and invite the other ops to join you there.

Channel Administration

#AHotTub is registered with the ChatNet IRC network's Channel Services group. This gives us access to the network's service bot K9. The registered channel owner is Charlie Robinson (CharlieR). Please feel free to talk to me at any time about any problems you may have in the channel. If you have a problem with one of the other channel operators, you should be aware that in most cases I will side with the op unless you can show that he or she has abused operator privileges in some way.

While I have tried to avoid establishing a hierarchical structure in the Tub, it's not completely avoidable. At this time (May 1997), we will be structuring the user list as follows:

Level 75

Level 75 access will be given in cases where the individual is not being added to the regular channel ops list in the near future. This in no way implies that access at this level makes you any less valuable to the channel than someone with a higher access level. The simple truth is that we want to get every Tub regular on the user list and give them access to K9, but we just can't op everyone. The ops need to coordinate their actions, especially in times of trouble, and too many ops make it very hard to do this. Therefore, we've decided that some members will be set up with this access level. Users with this access level can use the K9 commands Auth, Setpass, Help, Commands, Banlist, Kick, Comment, Ban and Unban. They do not have access to the Op command and will not have Auto-Op turned on in their user record. This is not to say that they will not be opped, just that another user with ops must op them manually. Generally these will be newer members, those with less experience on IRC and/or skill with the IRC and client commands, or those members who have indicated that they do not wish to be a part of the regular op corps at present. Level 75 members may be given temporary op privileges or they may have their access changed to Level 200 and be added to the regular ops group.

Level 200

Level 200 users will include most of the active channel ops. The active ops are those who have the Auto-op flag set in their user record, so that K9 ops them whenever they enter the channel. Level 200 ops are expected to be familiar with the K9 and client commands necessary to properly control the channel and are encouraged to attend the K9_101 classes and otherwise work on improving their skills so that they can help visitors and other channel members. In addition to the commands available at Level 75, Level 200 users have access to: Op, Deop, Invite, Suspend and Topic. No one will have Level 200 access unless he or she is committed to maintaining and improving his or her skills. The Level 200 members will not necessarily have longer tenure in the Tub than Level 75, nor are they "more important" than the Level 75 members. Users will normally move from Level 75 to Level 200 as the needs of the channel change, their skills grow, or their commitment to the Tub increases.

Levels 400 - 500

If you have a problem in the channel, a question, a comment or a complaint, see one of the members with Level 400 access or higher. They are the "executive committee" of the Tub. This is a deliberately small group because the need for access at these levels is limited. Level 400+ ops are skilled in both IRC and client commands, committed to the success of the Tub, and have shown themselves to be mature, level-headed in crisis and supportive of the purposes for which the Tub was founded. They are no more important ultimately to the success of the channel than the Level 75 users, but they help keep the channel owner from being swamped with administrivia.

Level 400 users have access to the Adduser, Remuser, Addmask, Remmask, Autoop and Mode commands, in addition to those accessible to lower level users. Level 400 and above are the Channel Owner's principal staff, with delegated authority to add and delete users from the user list, add logon masks when needed, and add or remove auto-op capability from a user's record. Anyone with Level 400 access or above can be assumed to be speaking for me unless I say otherwise. As of 9/6/97, the 400(+) level ops are: Judi, Mermaid, Quinn, Rags, and Rosie. Judi is the assistant channel master and is fully empowered to act on my behalf.

Finally, there is the Level 500 member, the channel owner -- me. Why am I the channel owner? I know at least one visitor has asked who put that idiot in charge. ChatNet only allows one "channel master" or Level 500 user per channel, and it's my name that was on the top of the channel application. I'm also the guy Channel Service comes to with comments and complaints, and I am ultimately responsible for the actions of all members of and visitors to the Tub while they are here.

ChatNet Channel Service Organization

ChatNet has delegated a specific group of IRCops to administer K9 and oversee the operation of registered channels. These Channel Service ops will normally only deal with the channel master, but they are available for assistance with channel takeovers and other emergencies. For more information on Channel Service, visit their Web site at http://cservice.chatnet.org. This site has a current list of all the members, by user number. It's indispensable for the Level 400+ ops, as many of the user list commands require a user number rather than a nick.

Where Do We Go From Here?

When Judi and I first talked about starting a hot tub channel on ChatNet, we never expected it would grow this much. I've resisted a formal structure for the channel -- a hierarchy of ops, written policies and such -- because I want this to be fun, not work. Because of the growth of the channel, I've had to change that view a little in order to keep it fun for me. I don't have any problem with delegating some of the responsibility or the authority to go with it. Other IRC channels have their own home pages and even newsletters. Frankly, I don't have the time to spend creating and maintaining a home page for #AHotTub. If someone else wants to do it as a learning exercise, let me know. The same is true for a newsletter. I will keep this Tub Guide up to date and I (or one of the 400-level ops) will maintain an ASCII version of the user list that you can use for ready reference. If someone wants to publish an e-mail newsletter, let's talk about it.

Want to arrange a get-together for channel members? If a group of Tubbers wants to meet in real life, that's great. Keep in mind, though, that we are scattered all over the US and Canada and that some of us are as far away as Germany and Australia. Some areas, like the Northeast and California, have a higher concentration of members than others. Members in those areas might want to arrange meetings regionally. And don't forget that many of us travel on business. If you're going to be on the road, why not invite one or more members from the area you're visiting to join you for dinner or drinks? Don't be surprised if some people are shy about a face-to-face meeting with someone they've only met online, but you might be pleasantly surprised.

I won't try to predict the future. I'll leave that task to the folks who run psychic hotline infomercials on late-night TV. All I can say is that you are all really fine people and I hope we can continue to meet and laugh online for a long time to come. If the opportunity comes to meet in person, that's even better. In the meantime, help yourself to the bar, leave your clothes and your cares in the locker room, and join us in the Tub for a while. We'll be waiting for you.

Reference Materials

Basic IRC Commands

IRC commands allow you to perform functions such as maintaining control of a channel and the users on it. The following list of basic IRC commands should help you get started. There are also mIRC and PIRCH Commands you can look at; consult the help and FAQ files for your client.

General Commands

/JOIN #channel

Join the specified channel.

example: /join #irchelp

This will make you join the #irchelp channel. Once on a channel, anything you type will be seen by all the users on this channel. The #irchelp channel is very useful, so say hello and then ask any questions you want. If the channel you specified doesn't exist, a channel with that name will be created for you.

/PART #channel

Leave a channel.

example: /part #irchelp

/LIST [#string] [-MIN #] [-MAX #]

Lists currently available channels. You can also tell mIRC to show only channels with a minimum and a maximum number of people. If you specify a #string then mIRC will only list channels with that string in their title.

example: /list

example: /list -min 5 -max 20

example /list #love

/ME message

Tells the current channel or query about what you are doing.

/MSG nickname message

Send a private message to this user without opening a query window.

/QUERY nickname message

Open a query window to this user and send them a private message.

/WHOIS nickname

Shows information about someone.

/NICK nickname

Changes your nickname to a new nickname.

/QUIT [reason]

This will disconnect you from IRC and will give the optional message as the reason for your departure. (this message only appears to people who are on the same channels as you).

example: /quit That's all folks!

/AWAY [away message]

Leave a message explaining that you are not currently paying attention to IRC. Whenever someone sends you a MSG or does a WHOIS on you, they automatically see whatever message you set. Using AWAY with no parameters marks you as no longer being away.

example: /away off to get something to eat, back in a moment!

/TOPIC #channel newtopic

Changes the topic for the channel.

example: /topic #friendly Oh what a beautiful day!

/INVITE nickname #channel

Invites another user to a channel.

Channel and User Commands

If you have Op status, the following commands give you control over both a channel and the users on it.

/KICK #channel nickname

Kicks named user off a given channel.

example: /kick #gb Ed

/MODE #channel|nickname [[+|-]modechars [parameters]]

This is a powerful command that gives channel operators control of a channel and the users on it.

Channel modes

------------------------

ModeChar Effects on channels

~~~~~~~~ ~~~~~~~~~~~~~~~~~~~

b <person> ban somebody, <person> in "nick!user@host" form

i channel is invite-only

l <number> channel is limited, <number> users allowed max

m channel is moderated, (only chanops can talk)

n external /MSG's to channel are not allowed

o <nickname> makes <nickname> a channel operator

p channel is private

s channel is secret

t topic limited, only chanops may change it

k <key> set secret key for a channel

User modes

-------------------

ModeChar Effects on nicknames

~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~

i makes you invisible to anybody that does

not know the exact spelling of your nickname

o IRC-operator status, can only be set

by IRC-ops with OPER

s receive server notices

v gives a user a voice on a moderated channel

Here a few examples of the MODE command:

To give someone Op status: /mode #channelname +o nickname

Giving someone Op status means giving them control over the channel and the users on it. Give this out sparingly and to people you trust.

To op several people: /mode #channelname +ooo nick1 nick2 nick3

To de-op someone: /mode #channelname -o nickname

To ban someone: /mode #channelname +b nickname (or user address)

example: /mode #animals +b Jiminy

example: /mode #tree +b joe@bloggs.edu

To Unban someone: /mode #channelname -b nickname (or user address)

example: /mode #gb -b Ed

To Make a channel invite only: /mode #channelname +i

You must now invite a user for them to be able to join your channel.

There are many more commands but this list should help you get started. To learn more about IRC commands you should download an IRC FAQ.

About K9

K9 is the ChatNet Channel Service bot. It provides channel administration and maintenance capabilities to channel masters and their designated operators. All channel operators should become familiar with K9's commands and how to use them. One way to do this is to attend the classes offered in #K9_101. The following excerpt from the K9 version 3.0 help file explains more about those classes.

K9 Classes

K9 classes are held for all who want to learn in #K9_101 on Sundays from 4-5pm EST and also on Wednesday's from 9-10pm EST.

Classroom Protocol: #K9_101

There will be times during the classes when #k9_101 is moded -m to take questions and comments. *PROTOCOL* will be observed during those times. This means that if you have a question, please type ONLY "?" (question mark). For a comment or suggestion, please type "!" (exclamation mark) only. Someone will be noting the nicks of those with questions and comments, and the order in which the request was made. You will be prompted by the queue keeper at such time as it is your turn to speak. When you have finished with your question or comment, please type "ga" (go ahead) to signal the instructors to begin their response. In this way we can ensure that all questions are answered in an orderly fashion. Please do not disturb the class unduly, as there will also be a bouncer present. Thanks for helping to make our newest service to ChatNet users a success!

Classroom Logs: #K9_101

Class logs can be obtained through HelpBot while you are on ChatNet. To get a list of logs available type: '/msg helpbot' logs and follow the instructions.

HelpBot

HelpBot is a tool put up by Channel Service for ChatNet users. He is crammed full of important information and if you ever need some quick info he is the place to look. To see Helpbots directory of help simply type from IRC window while connected to ChatNet: "/msg HelpBot help" Helpbot will then message you his help areas. HelpBot will message you something like this…….

<HelpBot> Welcome to the K9 information server.

<HelpBot> 1 Help With K9 Commands.

<HelpBot> 2 Previous Logs of K9 classes.

<HelpBot> 3 Frequently Asked Questions and Answers.

<HelpBot> 4 K9 help files.

<HelpBot> 5 Automated K9 troubleshooting.

<HelpBot> 6 Members of ChatNet's Channel Service and how to leave a message.

<HelpBot> 7 Information and updates on the New K9 classes available.

<HelpBot> Please enter the number according to your needs.

<HelpBot> ThankYou for using HelpBot written by Channel Service

<HelpBot> --------------------------------------------------

If you are within a query window simply type the command that you want. However, for IRC clients that don't have query windows you must type /msg helpbot <command> for instance: to get to the K9 help files section you have to type "/msg helpbot 4" If you have any suggestions on upgrades for HelpBot please email cservice@chatnet.org with the subject of "suggestion for HelpBot"

K9 Commands and Usage (Version 3.0)

For all commands, parameters entered in parentheses ( ) are optional, while parameters given in < > are mandatory. When typing in commands, neither ( ) nor < > should be typed, only the relevant information contained therein. Note: (/msg) is optional on all K9 commands, but should always be used for AUTH and SETPASS, for purposes of channel security. When using any other command in channel, ie without using the /msg, is it not necessary to type in the #channelname, provided the command you are using is for the channel in which you type it.

Level 500 : SAY ACT SND

Level 450 : ONJOIN JOIN PART STRICTT STRICTM

Level 400 : ADDUSER REMUSER ADDMASK REMMASK AUTOOP MODE

Level 200 : TOPIC

Level 100 : OP DEOP INVITE SUSPEND

Level 75 : COMMENT BAN UNBAN

Level 50 : KICK

Level 0 : AUTH SETPASS HELP ACCESS COMMANDS INITCHAN BANLIST

Access

ACCESS: (/msg) K9 access (#channelname) (nick)

Wherein: The #channelname is the channel for which the access list is being sought, or the channel in

which the person is on that you want access information on. Nick is the

current nick of the person in that channel.

If a listing of that channel's access list is desired, the format(s) is simply:

Examples: (/msg) K9 access (#channelname)

/msg K9 access #doghouse

K9 access #nuthouse

K9 access

This can also be used to discover the access level, if any, of a person in that channel at that time, with the

following format(s):

Examples: (/msg) K9 access (#channelname) nick

/msg K9 access #doghouse Ranma

K9 access Gibblets

Purpose: Shows a list of all individuals with K9 access for that channel, or when using the access "nick"

format, shows the access level, if any, of the person using that nick..

AUTH

AUTH:(/msg) K9@k9.chatnet.org auth (#channelname) <your password>

Wherein: The (#channelname) is the channel for which you are auth'ing and <your password> is the

password that you created with K9 when you SETPASS.

Example: /msg k9@k9.chatnet.org auth #doghouse yo7xšxø

Purpose: This command authenticates, or identifies, you to K9. You must AUTH with K9 each time you

re-enter your channel, before he will obey any commands. Please note that anyone with your mask who

knows your password will have as much control in your channel as you do. Please keep your password a

secret, and NEVER AUTH in channel!

BANLIST

BANLIST: (/msg) K9 banlist (#channelname)

Examples: /msg K9 banlist #nuthouse

K9 banlist #doghouse

K9 banlist

Purpose: Shows a list of all bans in the requested channel, including information on who

set the ban, date set, reason given (if any) and the date the ban expires..

COMMANDS

COMMANDS: (/msg) K9 commands (#channelname)

Examples: /msg K9 commands #doghouse

K9 commands #nuthouse

K9 commands

Purpose: Gives a listing of all K9 commands, depending on the access level.


HELP: (/msg) K9 help <command for which you require help>

Examples: /msg K9 help auth

K9 help addmask

Purpose: Provides a quick reference for the syntax of any K9 command, depending on the access level..

INITCHAN

INITCHAN: (/msg ) K9 initchan <#channelname> <key>

Purpose: Activates k9 for a given channel provided the channel is setup and approved and you have the proper key

SETPASS

SETPASS: (/msg) K9 setpass (#channelname) <your password>

Wherein: The #channelname is for the channel for which you are setting the password. The password is

created by the individual at the time they are given K9 access, and may consist of any combination of

words, numbers, or special characters.

Example: /msg K9 setpass #doghouse yo7xšxø

Purpose: This command sets up a password for you to identify yourself to K9. Also used to change

passwords with K9, but you must AUTH first..

KICK

KICK: (/msg) K9 kick (#channelname) <nick>

Wherein: nick is the current nick of the person that will be kicked from the channel.

Examples: /msg K9 kick #doghouse Wolf

K9 kick Cyclone

NOTE: K9 will not kick an auth'd person of higher access level than the requesting person

Purpose: to provide a means of quickly removing a person from a channel...

BAN

BAN: To ban someone while they are in channel: (/msg) K9 ban (#channelname) <nick> (time in minutes) (reason)

Wherein: (time in minutes) is the length of time for which that ban will last. A string of 9s is effectively a

permanent ban, equating to years.

Examples: /msg K9 ban #doghouse Wolf

/msg K9 ban #doghouse Wolf Profanity, harassing chanops

/msg K9 ban #doghouse Wolf 99999999

/msg K9 ban #doghouse Wolf 99999999 No rabid animals allowed in this channel!

K9 ban Ranma

K9 ban Ranma flooding, harassing chanops

K9 ban Ranma 60

K9 ban Ranma 60 Take an hour off to think about what you said.

To ban someone who is no longer in the channel, or no longer on the net: (/msg) K9 ban (#channelname)

<mask> (time in minutes) (reason)

Wherein: mask is the USER@HOST information that one finds upon a /whois or /whowas on an

individual, with wildcards properly in place of dynamic elements (elements subject to change).

Example: On a /whois HelpBot: HelpBot is helpbot@quantum.physics.isu.edu

/msg K9 ban #doghouse *helpbot@quantum.physics.isu.edu 5 Stop unbanning K9's bans!!!

NOTE: HelpBot's mask is always the same, or STATIC. Therefore one can ban it exactly as it shows on a /whois. For a DYNAMIC mask, or one wherein some part is subject to change, one should manually replace the dynamic element with the wildcard * as with this type of ban, K9 will ban only and exactly what he is given to ban. For examples of dynamic masks, see below. In both cases, the dynamic elements were replaced. These are the traditional positions for the dynamic in each type of mask:

Examples: On a /whois Gibblets: Gibblets is Josh@monroe-56.dialup.frontiercomm.net

K9 ban *Josh@*dialup.frontiercomm.net Spend a day studying.

NOTE: The above ban, lacking any given time parameters, is for the default time of 24 hours.

Example: On a /whowas DewMe: DewMe is ~durr@204.188.39.181 so:

K9 ban *durr@204.188.39* 9999999999

Purpose: Prohibits the banned individual, by USER@HOST, from entering your channel for a given period

of time from one minute to years. If that person is in channel when banned, K9 will kick immediately, as

the ban is initiated.

COMMENT

COMMENT: For a simple comment: (/msg) K9 comment (#channelname) <your comment>

Wherein: your comment is whatever you want K9 to say to, or about, you when you enter that channel.

This will be visible to everyone in channel as text.

Examples: /msg K9 comment #doghouse Oh boy, Cyclone's here!

K9 comment Hey, It's pHaNtAsY! She gives me great doggie treats!

For K9 to perform an action: (/msg) K9 $ACT (#channelname) <action you wish K9 to perform>

Examples: /msg K9 comment $ACT #doghouse jumps for joy to see his master again!!

K9 $ACT looks up, snorts and goes back to sleep.

For K9 to play a sound file: (/msg) K9 comment $SND (#channelname) <sound file for K9 to play> (comment)

Examples: /msg K9 comment $SND #nuthouse bark.wav barks!

K9 comment $SND wolfhowl.wav Strange are the Ways of the Wolfhearted!

K9 comment $SND K9grrrr.wav

For K9 to greet you by nick, no matter what nick you use the $NICK wildcard may be used anywhere in

the comment, and combined with any type of comment: simple, $ACT, or $SND.

Examples: /msg K9 comment $ACT #TwistedBlade_Inn greets $NICK enthusiastically!

K9 comment $SND K9party.wav parties with abandon that $NICK has returned again.

K9 comment $ACT curls up at $NICK's feet, off duty now that his master is back. :)

NOTE: All of the comment wildcards ($ACT, $SND, and $NICK) are case sensitive. They must be all caps

in order to work!!

Purpose: Strictly entertainment. :)

UNBAN

UNBAN: To unban a specific ban: (/msg) K9 unban (#channelname) <mask as it appears in K9's banlist>

Wherein: mask is the USER@HOST that appears in K9's banlist

Examples: K9 banlist shows -K9- BANNED FROM: 12/14/96 16:43:24

BANNED UNTIL:12/14/96 17:43:24

-K9- >

-K9- BANNED MASK:ablalock@*interconnect.net

BANNED BY:DKuntz

-K9- REASON:No bots in #Nuthouse

-K9- BANNED FROM: 11/24/96 19:33:14 BANNED

/msg K9 unban #nuthouse ablalock@*interconnect.net

K9 unban ablalock@*interconnect.net

NOTE: A shortcut method of unbanning is to take any part of the banned mask and surround it by wildcards * in the unban command:

Examples: /msg K9 unban #nuthouse *ablalock*

K9 unban *interconnect.net*

Understand that this will unban ANYONE on that channel's banlist with, in the first example, "ablalock" in their mask. In the second example, anyone with "interconnect.net" would be unbanned.

Use of the * wildcard may also be as follows:

Example: K9 unban *net

This will unban anyone and everyone on the channel banlist whose mask ends in "net".

Example: K9 unban *

This will unban ALL bans from that channel's banlist.

[This will unban a user from the channel even if the ban wasn't set by K9]

Purpose: To undo bans.

DEOP

DEOP: (/msg) K9 deop (#channelname) <nick>

Examples: /msg k9 deop #doghouse PAK

K9 deop Nicole

Purpose: To remove channel operator privileges from a given individual.

INVITE

INVITE: (/msg) K9 invite (#channelname) <nick>

Examples: /msg K9 invite #testing BP

K9 invite ShdowWolf

Purpose: To invite someone to your channel, especially if that channel is moded +i (enter by invite only)

OP

OP: (/msg) K9 op (#channelname) <nick>

Examples: /msg K9 op #nuthouse Hey_you

K9 op Dr-Who

Purpose: to give channel operator status to an individual

SUSPEND

SUSPEND: This command is not yet functional.

TOPIC

TOPIC: (/msg) K9 topic (#channelname) <new topic>

Examples: /msg K9 topic #TwistedBlade_Inn Welcome to ChatNet's premier fantasy role playing channel

K9 topic Clean friendly chat found here! : )

Purpose: commands K9 to create a new topic for the channel

ADDMASK

ADDMASK: (/msg) K9 addmask (#channelname) <USERID#> <nick>

Wherein: the USERID# is the first entry of a person's K9 access information. To find this information,

type K9 access in the channel and find that person on the K9 channel list. The nick is the nick that person

is using in the channel at that time, regardless of what nick is on the K9 access information.

NOTE: The person to be addmask'd must be in the channel in order to addmask him or her. This is necessary for K9 to "read" that person's new mask and add it to his database. There is no way to "manually" addmask a person.

Examples: /msg K9 addmask #nuthouse 4 [NT]

K9 addmask 3342 Mongoose

NOTE: An addmask is necessary ONLY if the entire mask has changed (new provider) or any part of the HOST portion of the USER@HOST mask is sufficiently different that K9 no longer recognizes an

individual's access. Changes to the USER@ part of a mask DO NOT CONSTITUTE A NEED FOR AN

ADDMASK! This information may be changed back easily by the person thru their IRC client (program).

Please see the help files for your IRC client for information on how to do so. Remember, the more masks

K9 has for that channel, the less secure the channel becomes!

Purpose: To add a new mask to K9's database when the entire mask, or any part of the HOST portion of

the USER@HOST mask has changed such that K9 will no longer acknowledge that person's access.

ADDUSER

ADDUSER: (/msg) K9 adduser (#channelname) <nick> <access level>

Wherein: access level is the access level for K9 commands that is desired for the individual.

Examples: /msg K9 adduser #nuthouse RB_on_Ice 500

K9 adduser Shirl 100

Purpose: To add a new user to K9's database for that channel, and to assign a K9 access level to that individual.

NOTE: A person should NEVER be appear on a channel list more than once. If there is a problem with that person auth'ing with K9, an ADDMASK is likely needed. If it is desired to change a person's K9 access level, REMUSER should first be used to remove the old access, then the person readded at the higher level.

AUTOOP

AUTOOP: (/msg) K9 autoop (#channelname) <nick> <T/F>

Wherein: T and F are for TRUE or FALSE. T, or true, means that the statement that K9 should autoop

that individual is true and desired, and will be carried out by K9. F, or false, meaning that K9 will not

autoop the person.

Examples: /msg K9 autoop #nuthouse Hey_you T

K9 autoop Tess F

Purpose: The autoop'd individual will be opped by K9 as soon as they enter the channel. K9 autoop nick

reverses this.

MODE

MODE: (/msg) K9 mode (#channelname) <+/-> <t, n, s, l, i, k, m>

Wherein: t, n, s, l, i, k, and m are all modes which affect the channel only. For an explanation of what each

channel mode does, please see the help files for your IRC client (program).

Examples: /msg K9 mode #doghouse +tn

K9 mode -si+pt

K9 mode +k blah

K9 mode -k blah

K9 mode +tnl 20

NOTE: to mode a channel -k requires that the key be known!

Purpose: Allows channel modes to be changed through K9

REMMASK

REMMASK: This command is not yet functional.

REMUSER

REMUSER: (/msg) K9 remuser (#channelname) <USERID#>

Wherein: the USERID# is the first entry of a person's K9 access information. To find this information,

type K9 access in the channel and find that person on the K9 channel list. The nick is the nick that person

is using in the channel at that time, regardless of what nick is on the K9 access information.

Examples: /msg K9 remuser #nuthouse 1215

K9 remuser 395

Purpose: To remove from an individual all access to K9 in that channel.

JOIN

JOIN: /msg K9 join #channelname

Wherein: The /msg K9 format must be used in this command.

Example: /msg K9 join #doghouse

Purpose: To bring K9 back to a channel from which he has been commanded to PART

ONJOIN

ONJOIN: (/msg) K9 onjoin (#channelname) <add/clear> <greeting>

Wherein: Greeting is what K9 will say or do to all individuals as they enter your channel.

Examples: /msg K9 onjoin #doghouse add Welcome to #Doghouse the ChatNET channel service channel.

K9 onjoin clear

NOTE: Multiple line list-fashion onjoins may be added in the following manner:

Examples: K9 onjoin add Welcome To #Nuthouse

K9 onjoin add ChatNet's Oper/Admin Channel.

K9 onjoin add Please follow these truisms while on irc:

K9 onjoin add Thou shalt not annoy.

K9 onjoin add Thou shalt not be easily annoyed.

K9 onjoin add Oh and /ignore works well too :c)

Purpose: To have K9 greet all those entering your channel.

PART

PART: (/msg) K9 part (#channelname)

Examples: /msg K9 part #doghouse

K9 part

Purpose: Makes K9 leave a registered channel until commanded to JOIN again.

STRICTM

STRICTM: This command is not yet functional.

STRICTT

STRICTT: (/msg) K9 strictt (#channelname) <T/F>

Wherein: T and F are for TRUE or FALSE. T, or true, means that the statement that the channel topic

may be changed only through K9 is true and desired, and K9 will "remember" and guard that topic. F, or

FALSE, means that the statement is not true, and K9 will allow anyone to change the topic, as is allowed

by channel mode.

Examples: /msg K9 strictt #nuthouse T

K9 strictt F

K9 strictt T

ACT

ACT: (/msg) K9 act (#channelname) <action K9 is to perform>

Examples: /msg K9 act #doghouse leaps up and starts chasing his own tail.

K9 act acts like a dog.

K9 act barks!

Purpose: Strictly entertainment! :)

SAY

SAY: (/msg) K9 say (#channelname) <what K9 is to say>

Examples: /msg K9 say #nuthouse I really get confused in here with so many masters to obey.

K9 say WOOF!

Purpose: Strictly entertainment! :)

SND

SND: (/msg) K9 snd (#channelname) <soundfile> (comment)

Examples: /msg K9 snd #doghouse K9party.wav parties with CServ!

K9 snd K9grrrr.wav growls fiercely.

K9 snd cbrown.mid

NOTE: K9 will perform an action after a sound file without the need for the ACT command. You must have a copy of that sound file on your hard drive, in the directory specified in your IRC client, to hear that sound file.

Purpose: Causes K9 to initiate sound files.

HELP

HELP: (/msg) K9 HELP (command name)

Examples: /msg K9 help unban

K9 help auth

K9 help strictt

Purpose: HELP!

K9 FAQ

Q. How do I register a channel?

A. Go to http://cservice.chatnet.org/ and use the Request K9 link.

Then fill out the form.

Q. Can you command K9 by typing with and without the /msg?

A. Yes. You can use in channel commands with K9.

For an example you could op someone in channel using this command

K9 op <nick>

As you can see you don't have to use the /msg or

the channelname.

Note: You cannont auth in channel.

Also see: commands

Q. Can I setpass without messaging K9?

A. Yes, but you should NEVER setpass in channel.

For security always use /msg for setpass

Also see: commands

Q. Can I auth without messaging K9?

A. No.

Also see: commands

Q. Can there be two 500 level masters in one channel?

A. No. You may see some channels that have two 500 level masters.

Those channels were made before the rule of one channel master per channel

was implemented and allowed to keep two level 500's.

Q. What is a mask?

A. A mask is the USER@HOST that K9 sees to verify who you are.

Q. What is a USER@HOST and how do I find out mine?

A. If you wanted to find out you user at host do a /whois on yourself

you'd get something like

NickName is email@something.somewhere.com * my real name

NickName on @#mychannel #doghouse

NickName using Pensacola.FL.US.ChatNet.Org ChatNet - Pensacola, FL -

NickName has been idle 15 seconds, signed on Sun Dec 08 01:48:53

End of /WHOIS list.

Now if you look at the line that says

NickName is email@something.somewhere.com * my real name

email@something.somewhere.com is NickName's USER@HOST

Q. Why when I look at my access K9 added a * in my mask?

A. K9 replaces dynamics (parts that change) with a *.

A * is called a wildcard and allows K9 to accept anything in place of

the wildcard.

Q. I know I've been added to the channel list but, where do I find

out what level I am?

A. Type K9 access in the channel you were added to or

type /msg K9 access <channelname>

Then look for your nick or mask in the list.

You'll see some thing like this

-K9- USERID: 9999 NICK:NickName

-K9- ULEVEL:200 PLEVEL: SLEVEL: 0 AUTOOP:T

-K9- LAST SEEN: 12/07/69 21:22:41

-K9- COMMENT:

-K9- MASK:*me@ 999.99.999.*

-K9- MASK:*email@* somewhere.com

The ULEVEL is the access level. So NickName would have level 200 access.

Q. How is it when I'm in a private channel, I still get messages from K9?

A. It's probably a Channel Service member broadcasting a message.

That makes K9 send the message to all people in channels with him.

Q. Is there going to be a nickserv on ChatNet?

A. That is a decision for the server admins to decide on and

for now there is no planned addition of a nickserv.

Q. Can you change someone's level without having to remove then readd?

A. No. This may be a command added to K9 in the future.

Also see: commands

Q. Is it possible to add someone on the k9 list when they are not online?

A. No. They must be online as K9 automatically looks up and adds

the mask for them.

Q. How do I know one of my channel operators needs an addmask?

A. Your channel operator could possibly need an addmask if he/she tried

to auth and got -K9- AUTHENTICATION FAILED! Better luck next time.

Check the mask that K9 recognizes your channel operator by and compare it

to the /whois on your operator. If they don't match you need to addmask.

Q. What if you had two computers each with separate modems and used different

nicks but the same address?

A. Then you'd need an addmask done for you.

Q. How many addmask can one nick have done?

A. As many as are needed.

Q. Can a 400+ user addmask themselves?

A. No. You must auth to addmask and if you need addmask you aren't able to

auth.

Q. Can I addmask for someone with a higher level than myself?

A. No. You can only addmask for someone of a lower level than yourself.

Q. How does a channel master (level 500) get an addmask done?

A. A channel master that needs an addmask done should come to #DogHouse and

ask a Cservice member to do it for them.

Q. Can I come to #DogHouse and get an addmask done even though I'm not a

channel master?

A. No. Due to the constant growth of ChatNet we cannot continue to addmask

for anyone under 500. You should see one of the 400+ level channel operators

for addmask.

Q. Is there any reason to remove a mask?

A. Yes. For security purposes. If a person has changed to another ISP

and won't be using that account again you should remove that mask.

Right now there isn't a remove mask command so, the only way is

to use remuser then readd.

Q. Why can't you just add a blanket mask to cover any ISP's you might have?

A. Two reasons. One that would not be very secure and two K9 looks up the

masks meaning there isn't anyway to manually input a mask.

Q. Does K9 see bans made by my IRC client?

A. Yes. K9 version 3.0 has been made to see all bans.

Q. How can I make a ban through K9 permanent?

A. There are no permanent bans with K9 at this time.

But you could use

K9 ban <nick> 999999999999999999999 <reason>

That's 21 9's the most K9 will hold

Also see: commands

Q. Can I have K9 unban someone?

A. Yes.

Also see: commands

Q. Can I have more than one channel?

A. No. The rule is you are only allowed to own one registered channel.

Q. After K9 went down for a "flea dip" he didn't get oped when he came

back up?

A. Usually all you have to do is have a 450 access channel op auth

then make him part and then make him join the channel again and he'll

op himself and all users will have full control again.

If that doesn't work please see a Channel Service member in #DogHouse.

Also see: commands

Channel Takeover Recovery Manual

Those pesky channel takeovers….

<Gibblets> first off

<Gibblets> if theres no proof that a crime was done, noone can be convicted and it will continue to happen

<Gibblets> all ops in the channel should keep channel logging on at ALL times

<Gibblets> even if you're away you never know what you might catch in your log

<Gibblets> A channel takeover can happen one of a few ways...

<Gibblets> someone could op someone, and that person then kick/bans everyone and takes the chan over

<Gibblets> make SURE you know who you're opping

<Gibblets> another method of takeover is by riding a netsplit

<Gibblets> this means..

<Gibblets> in ChatNet's network of servers

<Gibblets> sometimes the connection between servers breaks off

<Gibblets> thus they don't communicate with eachother

<Gibblets> say a server splits off

<Gibblets> the takeover person jumps onto that split server

<Gibblets> on that server, your channel may not exist

<Gibblets> so the user joins the channel and has ops

<Gibblets> once the servers link together again

<Gibblets> that user is still an op

<Gibblets> now current IRC Server programs running *supposedly* prevent that

<Gibblets> but people find ways to get around everything

<Gibblets> all ChatNet servers run the most up to date IRCD (server program) around

<Gibblets> but nothing is flawless

<Gibblets> if you see a user join the channel, and a server ops them

<Gibblets> that's when they rode in on a netsplit

<Gibblets> if this user is new to you, not recognizable at all

<Gibblets> then IMMEDEATLY deop

<Gibblets> without ops the person has to resort to channel flooding

<Gibblets> alright....

<Gibblets> IF k9 is in the channel, a takeover isn't possible

<Gibblets> the user CAN kick/ban everyone and mode the channel so you can't get in, but you can ALWAYS use K9 to reverse this

<Gibblets> a simple procedure with K9 for anyone with 400 access or above is as follows

<Gibblets> ./msg k9 ban #channel *!*@*

<Gibblets> ./msg k9 part #channel

<Gibblets> ./msg k9 join #channel

<Gibblets> once K9 bans everyone

<Gibblets> he kicks everyone out

<Gibblets> once K9 parts the channel

<Gibblets> all of the channel settings are erased

<Gibblets> and when he joins again, the settings are back to normal operations

<Gibblets> all bans are undone

<Gibblets> all mode changes are undone

<Gibblets> remember

<Gibblets> dont go into shock after this ;)

<Gibblets> the culprit is still there and waiting to be caught

<Gibblets> IMMEDEATLY /whois the user

<Gibblets> gather ALL of the information you can, ctcp version, whois info, anything

<Gibblets> and paste all of this information into a file.

<Gibblets> your logs and that file combined

<Gibblets> can gline that user for a long time

<Gibblets> and have the isp notified, good chance the users account will be pulled

<Gibblets> no isp likes to be glined from a good irc network

<Gibblets> if you DONT have 450 access to K9, go to #nuthouse for help

Thats all she wrote………

A Final Note...The Ident Server

On both PIRCH and mIRC, there is a facility called the Ident Server. Essentially, this service helps to identify you to the network. You should have your Ident Server configured and active in order to insure that you are properly identified to the network. We have a security problem with K9 opping users who are not on the channel list but whose User@Host combination matches an ID in our user list. This happens because in the past we have done Addmasks for users whenever K9 failed to recognize them. In too many cases, this resulted in a mask in the user list in the form "ident@domain". When a subsequent user from that same domain (e.g., Netcom) entered the Tub, K9 automatically opped him and he was then in a position to take over the channel. 1