International Internet Genealogical Society™
IRC Team Policy Manual
PART V - IIGS™ IRC NET ADMIN

SERVER ADMINISTRATOR

1. Within the IIGS™ IRC Net the Server Administrators are responsible to RootsWeb for the care, safekeeping, and proper operation of the servers and to the IIGS™ IRC Team to ensure that the servers effectively support the mission of the IIGS™ IRC Team.

IIGS™ IRC Team Approved DD MMM YY

IRC OPERATORS

2. IRC Operators (usually known as IRCops or OPERs) are the individuals most often charged with maintaining an IRC network of servers. IRCops should not be confused with channel operators though a user can be both an channel operator and an IRCop.
3. IRCOps are:
   1. here to help IIGS™ IRC users;
   2. usually identified through the use of the /motd command or by doing a /whois on an individual and looking for a line that says " is an IRC Operator";
   3. responsible to the Server Administrator and to the IIGS™ IRC Team to ensure that the IIGS™ IRC Net is operated in an efficient and effective manner in support of genealogical activities; and,
   4. encouraged to maintain a low profile in respect to their IRCop duties.
4. IRCops are not:
   1. omnipotent beings with limitless powers;
   2. responsible for monitoring the network users for bad behaviour;
   3. the enforcers of the laws of the land although on the IIGS™ IRC Net, because it is exclusively in support of genealogical pursuits, the IRCops may take on more of an enforcement role; and,
   4. usually involved in specific channel problems unless a serious breach of IRC rules has taken place.
5. IRCops actions are immediate and short-term and their actions are to be reported to the IIGS™ IRC Team for final disposition.
6. For additional reading material on IRC Operators we strongly recommend the IRC Operators Guide.

IIGS™ IRC Team Approved DD MMM YY

CHANNEL TAKE-OVERS

7. These uninvited events are an unfortunate fact of life on many nets and our IIGS™ IRC Net is no less susceptible to such unwanted incursions. With a little planning and care we should be able to reduce the risk of attack and minimize the side effects that such attacks often bring. If your channel comes under attack from a hacker/take-over artist, we strongly recommend you:
   1. resist the temptation to challenge the hacker;
   2. do a /whois on the hacker's nicknameand keep this information handy in case it is needed later;
   3. create an alternate "home" and move over to this new channel;
   4. use the /list, /who, /msg and /invite commands to:
      1. monitor new arrivals on the old channel; and,
      2. to invite these regulars over to the new channel;
   5. contact one of the designated IRCops and invite them in to take over the process of removing the hacker from our site.

IIGS™ IRC Team Approved DD MMM YY

CHANNEL ROBOTS

8. At this point in time, channel and/or server robots have not been approved for use on the IIGS™ IRC Net, excepting for specific trials approved by the IIGS™ IRC Team:
   1. an InfoServ Robot has been approved for a trial, with a final decision pending.

IIGS™ IRC Team Approved DD MMM YY

AUTO-OPS

9. Auto-ops is a built in feature of mIRC and other IRC clients that assists the channel management process. The mIRC auto-op feature can be set up to manage more than one channel. Auto-ops also provides a measure of channel protection but the user is cautioned that the use of auto-ops should not replace care and caution. Auto-ops is an excellent administrative tool that makes the granting of ops to the "regulars" on a channel that much easier.
10. Many channel robots, such as the eggdrop bot, and many net robots, such as DalNet chanserv and nickserv, are identical to mIRC auto-ops in that they use the user hostmask to establish identity and grant ops. IIGS™ IRC users and channel hosts are encouraged to take advantage of the mIRC auto-op feature.
11. Additional details can be found on the AUTO-OPS INSTRUCTIONS page.

IIGS™ IRC Team Approved DD MMM YY