ForeverChat IRC Network Acceptable Use Policy
Last Modified: July 10th 2017
This policy supersedes any and all policies issued before this date.
Jump to:
Section I. General network rules and policies.
I.1) Flooding. Flooding of channels or servers will not be tolerated. Persons who do so will be removed from channels and/or the network depending on the severity of the flood. Depending also on the amount of disruption, the network reserves the right to contact the ISP involved regarding the flooding.
I.2) Spamming. Spamming is not allowed on this network. Depending on the type of spam, you could be warned, kicked, banned, killed, or akilled. Channel founders may allow advertisements in their channels if they wish. However, this permission must be obtained before advertisements are sent.
I.2.A) Other network advertising. Persons who spam other networks on this network in any way, including by topic, message spam or other means, will be instantly akilled for 5 days. If a network is spammed more than once in a 24 hour period a notification will be sent to the DNS provider of the network spammed asking for them to notify the persons doing so of the likely violation of their AUP. Any channel on this network that is used to spam or advertise another network will be instantly forbidden, with the person being akilled for 5 days. Repeated incidents will result in longer akills and DNS provider notifications if it continues to persist.
I.2.B) Spamming of ForeverChat on other networks. Any person who sees this network being spammed on another should immediately provide a log to
akill@foreverchat.net for investigative purposes. Once the log is received, the hostmask provided will be akilled from ForeverChat IRC for a period of ninety days. This is to prevent channels moving here, or trying to get users here, from being able to do so. NOTE: All logs must be submitted to the address stated above.
I.2.C) Mass advertising. Mass advertising is defined on this network as either of the following: 1) Sending of an ad to more than one channel on the network without the channel founder(s) permission, and/or 2) Sending of an ad to more than one person via private message on the network. This will result in banning from channels and possibly the network, depending on the severity.
I.2.D) Advertising, right of the network to ban immediately. Spamming that occurs frequently of a particular site or domain may be akilled immediately if the host being spammed refuses to do anything about the spamming. These kinds of akills can be done at the networks discretion without warning. The decision to add a domain or certain spam to the list is the decision of the network itself.
I.2.E) Spamming of Outwar.com or similar sites (games where the spammer gets points for each person to follow the link) will result in an instant akill from this network. This includes spam via private message. Any spamming of this type should be reported to administration immediately.
ForeverChat IRC network will not allow harassment of its users by any person or persons on the network, or any entity.
I.3.A) Right to privacy. The operation of a channel and said contents of a channel are the responsibility of the channels founder. If the channel is not registered in ForeverChat IRC networks services, the responsibility resides with the person who has been on the channel the longest.
I.3.B) Moderation. The network will not moderate any channel due to its content, name, or any other reason. The network does not have the ability to log any content or chats on the network.
I.3.C) Enforcement. Unless requested to intervene in a channel by a user, the network will not enter channels with the intent to discover rules violations.
I.3.D) Illegal activities: ForeverChat IRC Network will only take action against your channel if we are given notice by a relevant authority that you are participating in illegal activities. We do not have the expertise or the time to interpret the law, and will leave that to the professionals. As we don't monitor your channels or private messages, we cannot be held liable for any activities that you engage in. As a user, you are still free to operate any channel you wish, with any modes set (private/secret/keyed) and will not force you to set any modes on your channel, BUT AS THE FOUNDER OF ANY CHANNEL, YOU MAY BE HELD LIABLE FOR YOUR USERS ACTIONS, AND ANY ACTIVITY THAT OCCURS IN YOUR CHANNEL(S). ForeverChat IRC can not and will not support you engaging in illegal activities. This applies to asking us where to download files or music or anything pertaining to copyrighted materials, including where to obtain full copies of said material, or how to defeat any protections placed on materials to prevent it from being copied or used. This policy requires the copyright holders to gather evidence of your illegal activities and ask the relevant authorities to instruct us to release this information to them. The network must stress though, that this can not stop you from being prosecuted if you participate in these illegal activities, as we are still required to co-operate with the authorities if they request us to. The network will not in any way attempt to compromise any investigation by a relevant authority, as this will cause the network to be liable also. The information the network keeps about you that would be release is outlined in section E, below.
I.3.E) Law Enforcement. The network takes no responsibility as to the contents or anything stated in or talked about on any channel on the network. The network does not log channels, nor does it have the capacity to do so. The responsible party for any channel content is the founder and/or the individual users of the channel. If requested, ForeverChat IRC network will provide, upon being served an appropriate court order, information regarding the registered owner of a channel/nickname. Except as listed below, the network does not keep nor will it keep any other information on users on the network, or what they may discuss or do in their channels. The following is a list of the information the network collects regarding users on the network, and if requested, the only information the network is able to provide if so ordered to:
I.3.E.1) Nickserv: Last known IP mask, email (this is provided by the user upon registration, the validity rests on the registrant) Last known quit messages. Last known time to be on. Date registration occurred.
I.3.E.2) Chanserv: Channels registered to a nick. Date of channel registration. Last known topic on the channel. Any modes "locked" on a channel.
I.3.E.3) If the person chose to register on the networks bulletin board service: Email address. Other information may be collected and will be provided if requested, however other information collected on the BB registration is optional and not required to use the network.
I.3.E.4) Information will only be released upon court order, and only by the Network Operations Team. No other person is authorized to release such information without the express permission of the Network Operations Team, and only upon the Network Operations Team being served with legal documentation requiring such information be released.
I.3.F) "Statistics" gathering. The network, or persons who operate channels on the network, may gather statistical data on the number of users in a channel, average number of users in a channel, or other statistical information. This information is for the channels use only and may only be used with the permission of the founder of the channel with stats being collected. A channel may ask that statistics gathering stop at any time. The gathering of and displaying of statistics about a channel or the network as a whole does not mean the network endorses a channels content, users, or anything else. Statistics gathering is provided to any channel on the network that requests such statistics be gathered and displayed for the channels personal use only.
I.3.G) Harassment via private message or in channels. Persons being harassed by persons in private chats should log these chats and contact local law enforcement authorities. The network cannot and will not log any messages that are transmitted via the network. If requested by court order, information to assist you with your case will be released, but only as outlined in section E above, as the network retains no other data for users using the network.
I.3.H) Channel disputes: The network will not be involved with channel disputes. Any dispute in a channel should be settled with the channels founder. The channels founder has the final say on bans, etc in a channel. The network will not remove bans placed on a channel except to enforce NETWORK rules. Channel rules are determined by the founder of a channel and should be discussed with that channels founder. If the channels founder chooses not to discuss it with you, you have no recourse but to start your own channel. The network is not responsible for the actions of channel founders or rules set by them.
The network reserves the right to deny access to any entity, person, ISP, or group of people if we wish. ForeverChat IRC network operates servers that are funded by individual persons who have the right to deny persons from the servers they directly pay for, and/or the entire network without reason or cause. Access to this network is not a right just because you have an internet connection, we may refuse access to any person we wish to not use our servers, services, or resources. Channel owners, operators, or other entities within the network also have the right to deny you access to any channel they operate for any reason they wish to do so. If you are removed from a channel, the network will not assist you in gaining access to a channel again. The person to contact regarding being banned from a channel is the channels founder.
I.5) Disputing of removal from the network. At the choice of the network itself or because of rules violations, you may be removed and forbidden from using the network. Any disputing of removal from the network requires the following process to be followed:
I.5.A) If you were removed by the network because the network has chosen not to allow you access to the network, you may not use the network until the network decides to allow you to do so again. If the network refuses to let you use the network, you simply will not be able to.
I.5.B) If you were removed by the network for a rules violation and feel you should not have been, you should email akill@foreverchat.net with a log and a statement of why you feel you should be allowed back onto the network. The network will review your case and decide if you should be allowed back onto the network or not.
I.5.C) The decision of the network is final on any ban from it. If the network chooses to not allow you onto the network for a period of time or permanently, the decision of the network is final. Use of ForeverChat IRC network is not a right just because you have an internet connection.
I.5.D) The network may also forbid you from using individual servers on the network for whatever reason it wishes to. If this occurs, use another server on the network that allows you to come on. The network may use "klines" which prohibit use of a particular server for any reason.
I.5.E) Channels may set any rules they wish and enforce them how they wish. If you are banned from a channel on the network, the responsible person is the channels founder. The network does not and will not have anything to do with internal channel operation or anything that occurs in any channel on the network.
I.6) Other rules. Although not outlined in this section, there may be other rules for usage of the network. When using ForeverChat IRC network, the entire AUP, as well as any rules listed in a particular servers MOTD, are in full effect while you use this network.
I.7) Disagreement with rules. Any person who does not agree with or does not wish to comply with, any rule listed in this Acceptable Use policy should disconnect from ForeverChat IRC network and never connect to it again.
Up to the top
Section II. Linking to ForeverChat IRC network, IRCop regulations and requirements.
II.1) Linking to ForeverChat IRC network. The following is required for any server wishing to link to ForeverChat IRC network:
II.1.A) Speed: at least 256k/sec both uplink and downlink.
II.1.B) Operating System: Unix or Linux OS only.
II.1.C) Permission: Permission must be obtained for the process to run.
II.1.D) Application: A fully completed application for link is required.
II.1.E) Application is voted on and approved by the current network staff as a whole.
At its discretion, the network may require a server to be testlinked before being permanently linked to the network.
II.1.F) IRCd. Any server linking to ForeverChat IRC network is required to run an unmodified version of the IRCd currently in use on the network. Modified versions are strictly prohibited, and if discovered, will result in immediate and permanent delink from the network. This network runs Unreal IRCd and the only allowable version is the version in use, and should be obtained from www.unrealircd.com only. No other versions of the ircd may be used. Such use will result in immediete and permanent delink from the network. The use of spymodes that may be available in any version of the IRCd is prohibited, any server linking to this network is required to disable all such modes, and the addition of any modes or code beyond that which is released officially by the coders of UnrealIRCd in the releases listed on their website is prohibited.
II.1.G) Any staff member in good standing may post intent to the BB to link a server. All postings of intent will be voted upon by the entire network to agree to allow the link, or disagree and not allow the link. All such votes will last for 7 days.
II.1.H) Any staff member who already owns a server linked to ForeverChat need not apply to link another one.
II.1.I) Any server approved that doesn't fall under II.1.G) or II.1.H) will be on a 30 day trial period. The trial may end in one of the following ways:
II.1.I.1) By the Network Operations Team or any Network Administrator, demanding a vote to determine status at the end of the 30 days
II.1.I.2) Any AUP violation will instantly cause the oper or server to be terminated
II.1.I.3) None of the above: the server will be linked permanently without revote.
The following restrictions are placed on any server linked to the network.
Staff: Limited to 1 Network Admin, 1 Server admin, 1 Co-Server Administrator, 5 Global IRCops.
Flags: Only administrators and above may be given the ability to "oper override" (flag v in operflags)
MOTD: A network MOTD is required to be placed on the top of any MOTD for a server linked to this network. This MOTD may be changed at any time. Server admins may add to the MOTD as they wish as long as the standard MOTD is used first.
Testlink: Any server linking to the network is required to complete a 30 day testlink period. While in this testlink period, only one IRCop is allowed (the NA of the server). No other opers may be added until the testlink is completed and a revote is taken on the server approving it for permlink.
The link application must list all potential IRCops that will be on the server when it is linked. Any NA with an objection to any staff member that may potentially be on the server may object to the linking of the server until the issue is resolved, or the person is removed from the potential IRCop list.
A server owner is usually the NA, however they may appoint someone NA and just be the server owner, or take another position on the server. If they own multiple servers, they may wish to do that to allow better coverage. They may also do this if they are not on often and want someone else to be in charge of the server. In network terms, the NA is in charge of the server they NA on. The server owner, however, is fully responsible for the server and retains control of the server itself, as they are the ones paying for the server or shell. A server owner may remove an NA at any time and reclaim the position, and/or do things to the server as necessary for its operation or maintenance. The server owner is always in charge of the servers shell and, because they pay for it, have the right to make any modifications or adjustments to it as the owner in order to comply with shell requirements, and/or because they feel like doing so. Even if not directly operated by the owner, the owner always has the final say as to what is occurring on a server-they do own it and pay for it.
The owner of a server on this network is expected to be easily and readily available to handle any issues with their server as needed by the network or events occuring on the network. This includes upgrades of the IRCd, changes to settings on the server, and other things that may be needed to be done to a server from time to time to ensure its proper and correct operation. Any changes to a server requested by the Network Operations team must be completed within 7 days of the request. Failure to do so will result in delink from the network as updates not completed in a timely manner may affect users, the entire network as a whole, or the security of the network. URGENT changes must be completed ASAP-and if a security risk, the network reserves the right to jupe a server and remove it from the random until the problem is fixed, if a major threat to the network exists due to the problem.
II.3) Becoming a staff member on ForeverChat IRC network.
The following is required for any person wishing to be a staff member on ForeverChat IRC network:
II.3.A) Be on the network at least 30 days with a registered nickname.
II.3.B) Complete an IRCop application*
II.3.C) The application is voted upon by all of the current network staff. If approved, you become a staff member. However, there is a 30 day trial period which may end in one of the following ways:
II.3.C.1) By the Network Operations Team demanding a vote to determine status at the end of the 30 days
II.3.C.2) The NA of the oper choosing to terminate the oper at the end of the trial period
II.3.C.3) Any AUP violation will instantly cause the oper to be terminated
II.3.C.4) None of the above: the oper will become permanent without revote.
II.3.D) If opering on any other IRC network, or becoming an IRCop on any other network while opering here, notifying the Network Operations Team of such opering in case any issues come up. Notification of this status is required within 48 hours of this occurring. If you do not notify the Network Operations Team of statuses on other networks, you may lose your oline for failure to notify.
II.3.E) Depending on the current staff situation, IRCop applications may be voted upon and approved, but if no positions are available, the person will be placed onto a holding list that they will be hired from when and if staff is needed on the network.
II.3.F) Server owners are NOT required to hire staff off the list if they choose not to. Except for staffing limits, it is up to the server owner as to how much staff they wish to have on their server. If a server admin wishes to have full staff or no staff-that is the decision of the server owner, the one paying for the server.
II.3.G) The IRCop application will list all of the restrictions outlined here and the applicant will have to agree to all provisions of the application before it is voted upon. If the applicant fails to agree to all provisions as outlined, the application will be rejected.
II.3.H) Completion of an IRCop application does not mean IRCops will be granted to an applicant. Even if the application is voted on and approved, network need as well as server owner choice will determine if a person is opered on the network. If no server owner wishes to pick up a person on the waiting list, they may not get IRCops even with an approved application. As server owners are responsible for the staff on their server, it is their choice if they wish to oper a person who was voted upon and approved. Approval of IRCop application does NOT guarantee oper status.
II.3.I) Oline and Server security. The owner of a server is responsible for the security of the server, including access to it via shell and olines on the server itself. Passwords for shells should be kept secure and changed often. Olines must be kept secure also. The use of *@* as the usermask in an oline is prohibited as this would allow any user obtaining that ID/Password to be opered. Any server with such olines in their conf without specific permission from Network Administration will be noop'd until these olines are corrected. If multiple ISPs are used for an oper, the oper should add separate lines for each ISP. If a security breach occurs and an oline and/or a server is compromised, that oper will be terminated as if the actions were done by the oper or server owner itself.
II.3.J) NA's of servers may, at their option, choose to hire an IRCop as a locop only for a maximum of 30 days. Locops will have no access to operserv or #staff and are intended to be used for evaluation purposes only. There is a 30 day time limit on this, and the oper must apply for ircops within the first 21 days as a locop as outlined previously in this section. If the vote is denied, the oper is to be removed as a locop after the 30 day period expires. If the vote is approved, the locop becomes a global operator. NOTE: Each individual server is limited to a maximum of 2 local operators at any time, and only if 2 or more positions are available, and 1 local operator if only one position available, or 0 if they are full on staff as outlined in the AUP. (Example: Server has only one position available, they can only have one local oper going for that position. If they have no slots available, they have no positions available and thus cannot have someone 'try out' for a position that doesn't exist). If the local operator fails to apply for IRCops in the first 21 days, they will lose locops on the 30th day and will not be opered until the application is approved. Any applicant who has applied for and been rejected in the last sixty (60) days may not be brought on as a local operator. There is no length of time nickserv registration required to do this as the oper will have a registered nickname for 30 days after the voting is completed and the locop period expires.
*Note: The network may restrict and/or not accept IRCop applications at any time for any reason. If applications are not being accepted, we are not seeking any new staff at the present time. Also, the application may be left online in order to gather applications from interested parties, but the network reserves the right to place approved applications on a holding list, and server owners may decide to hire off that list if they so desire.
II.4) Rules for Staff members on the network.
IRCops are required to behave appropriately while on the network. They are not to use oper powers to intimidate or harass users. They are not to join channels searching for a network rules violation unless reported to them by a user. They are not to set modes on themselves in a channel unless needed to solve a complaint by a user or founder of a channel.
IRCops are not to join any channel for the purpose of harassing people in a channel because they do not like the subject matter or a person in that channel. Personal issues are to be left out of oper decisions. Any oper using their powers to settle a dispute of a personal nature will be immediately terminated.
IRCops are to use all means possible to solve a problem before issuing a kill or akill. This includes ignore, ban/kick, and any other non "lethal" means before using kills.
IRCops who issue the kill command are to use a kill message that includes the reason for the kill, the rules section violated, and a warning that further indiscretions will result in a ban from the network.
IRCops who issue an akill should set an akill length of 5 days for a first offence, unless otherwise specified in the networks rules.
IRCops are not to akill entire ISPs unless necessary to prevent a problematic user from connecting.
Any akill issued on the network in excess of 5 days requires a full log showing the incident that caused the akill and a reason to be posted to the BB under the network akills section. Any akill not posted under this section of the board will be deleted. The first time this occurs the oper will be warned. Subsequent violation will result in suspension or termination.
Any IRCop who has a problem with another staff member, be it a rules violation or personal issue should speak to the person ranked above them.
IRCops are not to admonish or punish other opers on the network, unless they are their direct supervisor. They should contact their admin who will in turn contact the admin of the server that the IRCop causing the issue is on.
Any IRCop that violates rules may be warned, suspended, or terminated at the NA of the servers discretion. Severe violations may result in immediate dismissal and akill from the network. If the oper is doing something that threatens users on the network, they are to be akilled until the NA can be contacted.
IRCops are allowed to sethost or chghost themselves or clients controlled by them (bots, etc). They MAY set it on other users or opers with their permission only. Any IRCop adding a host for a user should not add a host that could be used by the user in an inappropriate manner (such as attempts to impersonate staff).
IRCops may be terminated by any member of Network Operations Team if they feel the oper is violating network rules or causing issues on the network that are affecting users or offending people excessively in channels not designated for such behavior. These terminations are to be completed immediately by the NA of the oper. If the NA refuses to do so, the server will be delinked.
All IRCops are required to be in #help when online and opered. All IRCops are to assist users when needed. IRCops must provide assistance to users as a top priority over anything else. They are not to insult users or refuse to provide assistance.
Any IRCop or staff member that is causing excessive disruption to the network for personal reasons or other reasons may be suspended or terminated depending on the severity of the disruption.
Any improper use of IRCop commands in channels or other improper use of commands will result in suspension or dismissal.
All rules on the network apply to staff members as well as users, and in cases of violation, IRCops may be terminated for violating any user rule.
Any user on the IRC network has the right to file a complaint against an IRCop for abuse of power or other behavior that an IRCop should not be doing. Complaints must be made to the Network Operations Team or the NA of the IRCop involved. All complaints are investigated, and if it is discovered that an IRCop is improperly using power, the IRCop may be suspended or fired at the NA's or Network Operations Team's discretion.
Any potential IRCop hiring must be submitted to the staff BB and voted upon by all staff before being added.
The network administration reserves the right to deny IRCops to any person known to be a threat to the network, or whose behavior on this or any other network would show that they should not be given the powers of an IRCop on this network. In order to do so, sufficient proof of the threat must be documented. Personal reasons are not sufficient for this. Any vote on an IRCop application can only be overturned by the Network Operations Team, and the Network Operations Team will only overturn a vote if sufficient proof is given.
The use of any script, code, or other means to attempt to intercept any chat or other activity on this network not occurring in publicly accessible channels is expressly prohibited. The use of any code to attempt to monitor channels that would hide the presence of someone in a channel to allow them to monitor it unseen is expressly prohibited. Any staff member finding to be running such code in IRCd or on the network to do so will be immediately terminated, and if being done with coding on a server, will be immediately delinked. Any person who suspects this is occurring should report such activities to the Network Operations Team with proof of such actions. Such activities are unethical and will not be allowed to occur on this network.
II.5) Departure from the network, resignation of IRCops/delink, etc.
II.5.1) Any server or IRCop who departs from the network due to AUP violations or abuse (ie is terminated) may not be considered for rehire for one year from the date of termination. To be rehired the oper must either apply with an IRCop application (if open) or be nominated to be on staff by a server owner, and posted to the BB. The Network may object to any rehire it feels would be disruptive to the network. In the case of server relinks, the server must apply for link just like any other server would. Previous tenure would not be used to qualify the server, and administration could reject the server if they feel the problems that had occurred before would occur again.
II.5.2) Departure from the network (server/ircop) resignation: Any person who departs from the network, be it a server or a IRCop, may not relink/reoper for 90 days from the date of resignation. This is to discourage/prevent people from leaving the network and coming back if where they departed to didn't work out, etc. People may depart the network whenever they wish, but if they want to return they need to wait 90 days. An oper returning must fill out a IRCop application or be placed onto the BB by a server owner wishing to hire said oper. Any server that wishes to relink must fill out and go through the link application process.
II.5.3) Departures for other reasons. Loss of internet services or shell services due to lack of funding or closure does not count for the purposes of this section. Servers lost or IRCops that depart due to these reasons may be readded or relinked as long as the request is made to do so in a timely manner, ie within 7 days of regaining internet access for an op, or within 90 days of loss of shell account for a server. Beyond this, a new application is required for link and/or a new ircop application or nomination by server owner is required for ircops. Any staff on a server that delinks must relocate to an active server within 30 days of the delink. Any staff that does not move to another server within this timeframe will be removed from IRCop status and must reapply for staffing. Persons on a server that is shut down or delinked should immediately seek an oline on another existing server on the network. All olines for staff on delinked servers will be deleted off the staff server after 30 days unless a new home is found for the staff member. Once a new home is found, the staff server information should be changed to reflect the new rank of the oper if changed from before.
II.5.4) The network reserves the right to not allow any staff member back onto staff if they feel they would be a threat and/or cause issues on the network.
Up to the top
Section III. Voting rules, Staff levels defined.
III.1) Staffing Levels. The following members of staff exist, and are ranked in this order:
III.1.1) Network Operations Team. The Network Operations team consists of 5 members who may implement AUP changes in emergencies without voting or discussion temporarily without consulting the Network. The Network has to approve all changes for them to become permanent. The Network Operations team may also submit AUP changes to the network at large for voting, such votes are binding and become part of or modify the AUP if approved.
III.1.2) Network Administrators. A network administrator can be the owner of a server or a person on the network that provides an essential network function. The network administrators are responsible for the servers they own or the network function they perform. They may make suggestions for change that can be implemented by a vote by the entire network. Network Administrators also have the right to remove any staff member on their server without vote or reason.
III.1.3) Server Administrators. A server administrator is appointed by the NA who owns a server. The server administrator is responsible for all staff on a server and also assists the NA in server operation. In the absence of the NA, the server administrator handles any action necessary by a server due to staff violating rules or any other occurrences.
III.1.4) Server Co-Administrator. The Server Co-administrator assists the Server Administrator in the duties outlined above.
III.1.5) Global IRCops. The global IRCops assist in operation of the server and assist the users of the server and the network. They enforce network rules and handle any problems on the server they are Opered on, and across the network as needed to help other servers on the network.
III.1.6) Notwithstanding the things outlined above, any oper on the network is required to:
III.1.6.1) Assist users as needed.
III.1.6.2) Enforce network rules.
III.1.6.3) Report any problems users or other staff are encountering to the Network Operations Team.
III.1.6.4) Behave in an appropriate manner while opered.
III.1.6.5) Never use more force than necessary to enforce a rule or to take care of a problem user.
All staff are required to be in #staff and #help when opered.
IRCops and other staff members may reside in other channels that are not network endorsed. When in any channel other than network channels (#staff, #help, #irchelp) the network is not responsible for their actions except for actions taken in enforcing rules set on the network. The presence of a staff member in a channel does not imply that the network supports or endorses any behavior in a channel.
III.3) Voting rules.
III.3.1) Network rule changes can be implemented by the following people, or in the following ways:
III.3.1.A) By a vote of the entire networks staff.
III.3.1.B) By the Network Operations Team without a vote, in emergencies.
III.3.1.C) By the Network Operations Team, with a vote by the Network.
III.3.2) New rules, if implemented, cannot be modified or changed (ie, a vote to reverse the change just made) for a period of 90 days from the enactment of the rule, except by the Network Operations Team in cases of extreme emergency.
III.3.3) Voting options will be as follows:
IRCop applications
Yes = Vote the oper in as an IRCop (30 day trial period)
No = Do not accept the person as an oper, reject the application.
Link applications
Yes = Vote the server in as a link. (30 day trial period)
No = Do not accept the server for link, reject the application.
All other votes:
Yes = Accept
No = Reject
III.3.4) Any and all votes on the network will last 7 days. This includes compliance checks, link applications, ircop applications, or votes for delink, etc.
Up to the top
Section IV. Delinks and terminations of staff.
IV.1) Any server, or server owner, that grossly violates the AUP; or somehow causes the network to be insecure; or facilitates in the network being insecure; or causes major issues to the network and its staff or its users, or both; or abuses powers granted to them by the network against fellow staff and users; or grossly misrepresents the network and its standards; or refuses to enforce rules as stated in the AUP; may be delinked from the network for said violations.
The process which will be taken against a server that falls into the above category will be as follows:
IV.1.A) The server will be juped from the network and removed from the DNS and placed on suspension by a unanimous vote of the Network Operations team and a resulting vote by the Network NAs (or immediately if the matter, being left unchecked, would cause damage to the network).
IV.1.B) A vote including all evidence of said violation will be posted by the Network Operations team indicating what the violation was. The choices in this vote will be: 1) Allow the server to relink while on probation* for a period of no less than 90 days, 2) Allow the server to relink without any restrictions, or 3) Delink the server from the network due to the violations that occurred.
*Probation is only available if the server is not previously on probation for rules violations-if the server is already on probation, then the only choices in the vote are 2 or 3.
IV.1.C) Depending on the results of the vote, the server will be relinked or removed from the network. In the event of being removed, the server or its owner may not relink or hold any level of staffing for a period of one year from the time of delinking.
IV.2) Any staff member that grossly violates the AUP; or somehow causes the network to be insecure; or facilitates in the network being insecure; or causes major issues to the network and its staff or its users, or both; or abuses powers granted to them by the network against fellow staff and users; or grossly misrepresents the network and its standards; or refuses to enforce rules as stated in the AUP; may be suspended and/or terminated from the network for said violations.
The process that will be taken against a staff member that falls into the above category will be as follows:
IV.2.A) The staff member in question will be removed from oper status by either the network operations team after a unanimous vote or immediately if the matter, being left unchecked, would cause damage to the network, or by the NA of the server the oper is on staff. (Note: Nothing in this provision prevents an NA from removing a staff member on their own server without a vote if they didn't do what is outlined above, but if they do not wish that person to oper on any other server on the network, this procedure must be followed)
IV.2.B) A vote will be posted by the Network Operations team, or NA of the server on which the oper gains access. The vote will include any evidence of the violation. The choices that will be presented are: 1) Suspend said oper for 15 days. 2) Suspend said oper for 30 days. 3) Re-instate oper with no restrictions. 4) Terminate oper for behavior.
IV.2.C) Depending on the results of the vote, the oper will be suspended, reinstated, or terminated.
IV.2.D) Depending on the number of prior violations, the Suspension option may not be used for the vote. This decision is up to a unanimous decision of the Network Operations Team . Unless the NA of the server participated in, or encouraged the oper to do what they did, no punishment will be levied against the server the oper is a staff member of.
IV.2.E) Any NA suspended for any reason that is on the Network Operations team loses said position due to suspension. The network has decided that people on the Operations team must be held to a higher standard.
Section V. Services.
Services are provided to Users on ForeverChat IRC network as a convenience tool and a tool to allow channels to be registered and protected. Use of services to register a channel or nickname does not constitute network support or endorsement of a users' or a channels actions on the network.
Nickserv.
Nickserv allows for the registration and retention of nicknames on the network. It also allows nicknames to be given access in Chanserv for channels. Persons who abuse nickserv or use it to register nicknames they do not intend to use including registration flooding may be denied access to Services by the network.
Chanserv.
Chanserv allows for the registration and retention of channels on the network. It allows for channel control and modes to be locked on a channel, as well as topic retention. Persons who abuse chanserv or use it to register channels they do not intend to use including registration flooding may be denied access to Services by the network.
Memoserv.
Memoserv allows for the sending of memos to other registered nicknames. Use of memoserv for any purpose other than communication with other registered nicknames (such as memo flooding) will result in access to Services being denied to that user.
HostServ.
Hostserv allows you to use a different Vhost of your choosing while identified and on this network. Abuse of HostServ, including use of a host to impersonate someone you are not, or to attempt to entice or otherwise harass users will result in you no longer being allowed to use this service, or access to Services being denied to you.
Other Services.
There are other services available to users on the network that are not specifically outlined in this section. Abuse of any network service will result in denial of access to services, or to the network, at the networks discretion.
Up to the top
Section VI. Other provisions.
Use of network: The use of this network by any person is strictly at your own risk. ForeverChat IRC network is not responsible for any content on the network. If you choose to send or receive files in any fashion, the network takes no responsibility for doing so, or for if you receive a Virus or other problems with said file. Anything you do on this network is at your own risk. You, and only you, are wholly responsible for your actions while using this network, and for following all rules outlined in this AUP while using the network. Use of the network constitutes adherence to the policies stated in the AUP, not reading the AUP does not exempt you from the policies stated herein.
Services: Services are provided as a convenience to users on the network. The network is not responsible for anything that may occur due to services downtime, outage, or loss of data. Services are provided to you without charge and thus come with no warranties, expressed or implied.
Access to network: Access to this network may be forbidden to any user without reason or without any notification.
Proxy Scan: Any client connecting to this network is scanned for open proxies upon connection. You may be scanned each time you access the network. If you reside in any country or locality that does not allow such scans to occur, or you do not wish to be scanned, you should not ever connect to this network.
Up to the top
