############################################################################ # Slacknet IRC Operator Rules and Procedures (Updated: 2008-05-01) # ############################################################################ IRC Operators (ircops) are administrators on Slacknet IRC Network (Slacknet) that not only maintain their respective servers, but the network as a whole in order to preserve a wonderful environment for chatting to take place. Naturally, there are users, which will cause trouble on the network, typically harassing users, but also sometimes attacking servers. The main purpose of an ircops is to protect the users and servers from unwarranted attack. This document details rules that ircops must follow and procedures they must use in order to keep the network in order. If any of these rules are broken, it can lead to an ircop being removed from his or her position for good. [ Overall Network Rules ] Each server has its own rules, however some rules are set by the network and cannot be overridden by servers. 1. No Flooding or mass CTCP 2. No Spamming 3. No Proxy / Wingate / SOCKS connections 4. No attacks on the server or its operators 5. No more than 5 clones per host 6. No warez, child pornography, or bot nets [ Administration ] The overall administration of Slacknet is built up of three different groups. These groups delegate power and create and enforce policy. < Network Presidents > Represented by mode ~ in #opers The network has two figureheads of sorts, they are not dictators, rather this position is a way to keep things running smooth and balanced. In order for something to pass, such as a promotion of a user or operator, or a new network policy, it must be approved by the Network Presidents and the Network Administration. Originally, this position was dedicated to the two founding operators of the network, however in the event one of them steps down, he or she can put another person in his or her place. < Network Administration > Represented by mode & in #opers Network Administrators are the server owners. Typically each server has one owner and this owner is automatically a network administrator (once the trial link is completed) and therefore has the ability and responsibility to appoint local ircops. It is not recommended that servers have more than one owner, however it is possible for them to have two, but no more. Each server (i.e. server owner) has one vote in the Administration, even if the server has two owners, and it still only represents a single vote. If one person owns three servers, for instance, he or she has three votes. Server owners can appoint local ircops, however these operators can only be local, and thus local rules apply. They shall not have any global abilities, that includes global kills, and various other powers. When promoting a user to a local ircop, a lot of things must be taken into consideration. The administrator must know if the new ircop would abuse his or her power, if he or she is actually skilled in IRC and computers, and whether or not her or she is dedicated to the network and will actually help users. If there are any doubts what so ever, a user should not be promoted. < IRCOP Administration > Represented by mode @ in #opers This is made up of all the ircops that are not server owners. They do not have the ability to do anything global. The reason they have their own organization is so that they can vote on a new server. See the server section of this document for more information. < Trial Server Owners > Represented by mode % in #opers Trial Server Owners are not yet network administrators and therefore should have no global powers and cannot vote. However, once the trial is complete, he or she will be promoted to network administrator. See the server section of this document for more information. < Trial Server IRCOP > Represented by mode + in #opers Like the Trial Server Owners, these people have no power aside from local abilities. See the server section of this document for more information. [ Servers ] < New Servers > All new servers must fill out the server application, even if the owner has more than one server on the network. The configuration must be double checked by the network presidents and approved before the link can take place. This must be sent via email or DCC to the network presidents and any changes made by them must be used on the new server. All servers must provide host, user, and password to the network presidents incase something happens. The information will be kept completely private and encrypted, and will not be abused. < Trial Links > If an application has been accepted, the server will be linked (following the rules in the "New Servers" section) and in trial for 30 days. If after 30 days every network administrator and ircop approves the new server, the server can stay permanently linked. At such a time, the server owner will be made a network administrator and promoted to global abilities. < Removing Servers > [ Services ] Services are extremely sensitive, and therefore only a few different ircops have the ability to access parts of it beyond the simple administrative front end. Typically the Network Presidents and 1/4th of the Network Administrators will have OperServ access. New Network Administrators are not able to obtain this ability, and typically the user must be trusted by all other ircops before promoted. [ Users ] < vHosts > All established users are allowed to have vHosts. They must do this by requesting the vHost and having it approved by a server administrator. Once the request has been made, they can notify the ircops in #help and at such a time, it will may or may not be accepted. All vHosts must be of non-existant top-level domains, that is a vhost can end in .hotdogs, but not in .com. Some users may claim to own the host, but even then it is not allowed, as it creates confusion that it is a real host, when it is not. < Kill > Users should only be killed when they are causing problems with other users or are causing problems with ircops. A kill should always be used before a K:Line or G:Line. Local ircops should only be able to kill local users, if the user is on another server, the local ircop can request a network administrator to kill the user. If the user is killed by proxy, then "kill requested by localircop" must be used in the kill message. < K:Lines > K:Lines can be set by any ircop and are only local. Remote k:lines are only allowed by Network Administrators. < G:Lines > G:Lines are network-wide bans, and should only be used when a user is a danger to the entire network, not just one server. < Opless Channels > If a channel is opless, that is lacking ~, &, @, and % and the channel is registered, opers cannot step in -- it is up to the channel owner to maintain ops in his or her channel at all times. If the channel is not registered, the oldest existing five users with verified ident will be opped.