When you operate on the IRC4Fun Network, you agree to be bound by the following rules. If you do not abide by the following rules, you may find yourself faced with Corrective Actions, up to (and including) suspension/termination of your access/O:line(s).
IRC Operators and Server Administrators are users too, and bound by the same Acceptable Use Policy as Guests are. As an IRC4Fun Staff member, you are expected to conduct yourself as a Role model to our Guests.
- You agree to follow the Acceptable Use Policy (AUP) as well as this Acceptable Operating Policy (AOP)
- You will be polite and professional while /Oper’d up or using your Access.
- You are not required to participate in #IRC4Fun, but it is highly RECOMMENDED.
- IRC4Fun Staff will not become involved in Channel disputes. (Involving channel bans, settings, ops, etc)
- IRC4Fun Staff will not go on other IRC networks and cause disturbances or violate other networks’ rules.
IRC4Fun Staff has access to resources intended to help serve IRC Operators, Services Team, and other Staff officials with various network-related functions. These resources are typically not available to our Guests, and use of the resources is monitored at all times to prevent abuse. Below are some of the resources available, and their standards:
- OperServ (Network Staff Service) – OperServ is the IRC4Fun IRC Operator and Services Team central control service. It is used to aid Network Staff with G-lines, MODE changes, Services related functions, etc.
- Server O:line (Operator Access) – Your O:line gives you access to functions on the IRC Server it is added to, depending on the access level(s) assigned to it.
- Services (Services Access) – Your access to Services provides you the ability to perform functions with NickServ, ChanServ, and all other Services bots to help IRC4Fun users with problems/questions and provide support to IRC Operators.
Access Restrictions (X:lines)
From time to time, it will be necessary for IRC Operators/Administrators to add access restriction lines (X:lines) to prevent abuse. Refer to the below guidelines as to which access restrictions should be used, and when. (NOTE: IRC Operator/Administrator access should never be abused by using Access Restrictions (X:lines) or forced disconnections (KILLs) unless absolutely necessary to stop abuse or prevent further abuse. As an IRC Network, we want to grow; and should (as a business would) try to correct behavior as opposed to getting rid of a guest.)
- Kills (Forcing user to be disconnected from IRC4Fun) – KILLs may be issued as a first alternative to Access Restrictions (X:lines) to stop/prevent abuse.
- K-lines (Local Server Ban) – K:lines may be added by Server Administrators/IRC Operators for any reason they choose, if any.
- G-lines (Global IRC4Fun Ban) – G:lines should only be added for violations of the IRC4Fun Acceptable Use Policy (AUP) or mass global removal from the network. Individual Server Policies should be enforced with local K-lines, however under certain circumstances are enforced by global G-lines in special cases.
- Z-lines (Global IRC4Fun IP Ban) – Z:lines may be added for DNS Blacklist matches as well as violations of the IRC4Fun Acceptable Use Policy (AUP), and are typically used only by the Open Proxy monitors. Individual Server Policies may be enforced with local K-lines, however Network Policies are enforced by G-lines.
Abuse of Privileges
- Using OperServ to manipulate a Channel’s modes/ops/bans while not attending to official network activity.
- Using NickServ or ChanServ to manipulate access to a nickname or channel where you do not have access and are not attending to official network activity.
- Retaliating against users and/or other IRC4Fun Staff
- /KILL‘ing a PyLink Remote user (a user that is not connected to IRC4Fun, but is connected from another network via PyLink or *.relay) for any reason (Kills to PyLinked users will be bounced back – best to just chanban them)
- Use of /SAJOIN, /SANICK, /SAPART or /OJOIN when not attending to official Network business. /SAJOIN, /SANICK and /SAPART use without valid reason is abuse of privileges.
- Server Administrators are IRC4Fun’s central management team. Each Server Administrator casts a vote on changes to the network, policies, routing, linking/delinking, etc. per Server they administer. (Example: If a Server Administrator has 3 servers linked, that Administrator would have 3 votes per issue/topic)
- Server Administrators are responsible for maintaining a stable, safe server for IRC4Fun clients to chat on.
- Server Administrators may NOT add local/global IRC Operators or staff without prior approval from other IRC4Fun Administrators (a vote)
- Server Administrators are responsible for ensuring that their staff follows this Acceptable Operating Policy (AOP) as well as the IRC4Fun Acceptable Use Policy (AUP).
- Server Administrators are responsible for ensuring that their staff is Correctively Actioned upon abuse.
- In the event that the Server Administrator refuses to Correct actions taken by it’s operators; a Corrective Action may be taken towards the Server Administrator and the Operator or Helper. The administrator and staff member in question may be prevented from /OPER’ing up, or the administrator’s server may be forcibly split from the network and JUPEd.
- Servers that split and remain split 30 or more days will be subject to automatic delink.
- Server Administrators that go MIA for 30 or more days can be subject to delink and/or removal of access to the network, DNS removal of linked (or split) server.
- Periodically updates will be issued for our IRC Server Software (InspIRCd):
- Security Releases: When an update is released due to security purposes, each server will be expected to update within 24 hours. If a server has not updated a security release within 24 hours, IRC4Fun Admins will take a vote on having the server JUPEd until it complies. If compliance doesn’t occur within 7 days; the server will be juped and IRC4Fun Admins will take a vote on permanently delinking the server.
- Normal Releases: When an update is released, it is strongly recommended that all servers update their software within 14 days. All servers must update their software on normal releases within 30 days of the software release date.
- Incompatibility Updates: When an update is released that may be incompatible with previous versions, a vote will be initiated for IRC4Fun Admins on whether and when to update.
- InspIRCd Modules: Only approved modules may be loaded. No other additional InspIRCd modules may be loaded without prior approval from IRC4Fun Admins (as the modules loaded must be the same on all servers) No IRC4Fun server (client or hub) may utilize any “spy” modules, devices or functions. Failure to comply with this policy will result in immediate jupe and delink process for the violating server. *Attempting to load un-authorized modules can also result in your server immediately squitting from IRC4Fun.
Consequences for Violation
- If you violate any rule or regulation stated in this document, you will be subject to progressive disciplinary action, including but not limited to suspension of privileges, forced removal from the network, or even delink or having applicable server JUPEd where necessary.
- Server Administrators are responsible for their Staff, and for Corrective Actioning them upon abuse. Server Administrators may call for a vote to Corrective Action other Server Administrator’s where abuse has been committed and requires Corrective Action.
Appealing a Violation
If you are suspended from privileges or denied access to an IRC4Fun server or the entire network, you should follow the procedure outlined below. Please note, however, that IRC4Fun server administrators are under no obligation to take any further action.
- If you are a Local or Global Operator, contact your server administrator, explaining how future incidents can be avoided.
- If you are Server Administrator, contact abuse-com @ IRC4Fun.net, explaining how future incidents can be avoided.
Last Updated: 08/26/2016