|
|
This document dated March 3, 2006 supersedes all previous documents
relating to IRCops regulations, rules, and guidelines.
Without the assistance, loyalty, and co-operation of all the IRCops,
AwesomeChat Network would not be what it is today.
The Administrative staff still hopes that you get the most from your
IRC experience; this includes making friends with others, learning new
skills and having some fun. We all need to remember that IRC is about
chatting and meeting people.
The authors of this document welcome you to the AwesomeChat Network
and hope you enjoy your time with us as both as user and a member of
the IRCop team.
Introduction
An IRCop is not a cop. You are an IRCop (Internet Relay Chat Operator)
there is a difference.
Without the users there is no need for a network. That one constant
applies to all IRC networks. It is therefore important that you remember
that even though you are an IRCop representing both your Server Admin
and the whole network, you are still a user.
You as an IRCop are not here to abuse other users or each other, nor
are you here to enforce channel rules. You are here to enforce local
server policy and Network policies.
This document contains the primary guidelines and policies of AwesomeChat
Network as defined by the NetAdmins. These are subject to review and
change at any time. The Awesomechat Network will make every effort to
assure that this charter is kept as current as possible to ensure that
the users and operators are given a recent set of policies and rules.
It is the users and Operator’s responsibility to read this document
and any others dealing with the operation of this network.
- To provide users with a hassle free chat environment.
- To treat all users fairly, and with respect.
- Offer user-friendly services and help for new users with those
services.
- To establish a network with helpful IRCOps who are willing and
able to offer assistance to users during their stay on AwesomeChat.
- To provide a user friendly network where small based servers can
link.
- To use their best judgment when the commands kill, gline, akill
are called for.
- To utilize OperServ in such a way so as not to be accused of being
power hungry or breeching IRCop rules.
- To abide by the channel rules of any channel you are in.
- To ensure that Network policies, business, problems, and /or complaints
are not discussed in open or non Network Channels.
- Not to correct or embarrass another IRCop or ChanOp in a channel.
- Never give out personal information relating to another IRCop or
passwords.
- This is an INTERNATIONAL network and we seek to provide people
of all nations and languages a chance to speak.
Section 1. General Rules:
- No more than 3 connections per user.
- No nuking/DoS attacks on users.
- Do not harass other users or IRCops.
- No abusive behavior of any kind. Such as flooding, abuse, harassing
other users, mass messaging and advertising.
- Please do not ask for O:lines.
- Advertising any other network or site publicly or by private
message for the purposes of causing harm can result in an immediate
Gline
- Inviting a user to join another network or Web site within channel
or private message to a user, or by means of mass messaging in an
attempt to cause harm, may result in a Gline
- Kiddie/rape/animal/incest will not be permitted. Where this type
of file transfer or advertising of such comes to notice action will
be taken. Channels dealing with the trading of these kinds of materials
will be shutdown and its user’s akilled/glined without warning.
- Channels that deal in trading of exploits/credit card numbers/hacked
shell accounts will be shut down. Users attempting to trade such
things will be akilled/glined without warning.
- Anyone found to be a security risk to this Network can be removed
without warning.
Section 2. File Swapping /Sharing and Warez
Disclaimer:
The Awesomechat Network does not regulate in any fashion the transferral
of files between its users. It has always been the policy of this
network to maintain a “hands-off” policy. In accordance
with this policy, anyone who transfers files agrees by the acceptiance
of the file, to hold the Awesomechat Network and its staff harmless
for any damage done by the transferring or installation of files.
We (The Awesomechat Network) will do our best to assure there is a
safe environment for the chatting and transferring of data, but we
make no guarantees either expressed or otherwise that any file is
safe.
By sharing or swapping files the user must accept responsibility
for their own actions and agrees to accept any risks of prosecution
by regulatory authorities. In the event that a Govermental or Law
Enforcement agency should make a request for documents, this network
and its staff will do everything within its power to comply with such
requests and court orders.
Section 1. User Rights:
- To chat on the network in peace without other users flooding,
harassing, and disrupting their chat.
- In regards to a users nickname, the users maintain the following
rights and privileges:
- To register their own nicknames.
- To have such name not interfere or cause harm to another
user or IRCop. In the event a name is found to be offensive
and or abusive, the person or persons shall be given the opportunity
to change the nick to something that is non offensive.
- To register their own channel and establish and enforce rules
of their choosing without interference from IRCOps, Server &
Network Administrators as long as such rules don't violate the Network
policy.
- If G:lined have the right to ask the G:line committee and appeal
their G:line and the reason for the G:line. This Gline email is
to be listed on the official web page.
- To seek the help of a IRCop to assist in a matter that is a network
matter, The users should join the official help channel #help if
they need assistance. The staff of that channel will do their best
to assist them in any way possible. In the event there is a lack
of staff there, the user may use the /helpop command.
- To ask an IRCop to look into the actions of a IRCop or Admin
to decide if he/she is abusing powers. NOTE: This is considered
a very serious matter and the filing a false report of abuse of
powers on an IRCop can result in your removal from this network!
Section 2. User Responsibilities:
- To be courteous and respectful to other users and AwesomeChat staff..
In other words, treat people the way you wish to be treated.
- To abide by channel rules including on-join advertising, and general
advertisements in the channel
- Never attempt to abuse or misuse any of the Network services or
bots.
- To not harass, flood, takeover, or mass message another user, channel
or IRCOp.
- A user will not for any reason post a URL or send a file that has
malicious content. Anyone found posting URL’s or transferring
files for the purpose of causing harm to a user or their computer
shall be immediately removed from this network.
- The Awesomechat Network is a family safe network. (Note please
this does NOT mean that all channels are Family oriented. The following
guidelines are in place to assure the safety of our users and IRCops:
- At no time shall and adult (heretofore defined as a person
who is over the age of 18) Solicit a minor (a person who has yet
to reach 18) for immoral or illegal purposes. Any adult found
breaking this will be immediately removed from the network and
possible legal action may occur.
- At no time shall a minor, knowing it is forbidden to do so,
seek to solicit an adult for immoral purposes. As it is clearly
stated in this document, it is the responsibility of the users
to be aware of the rules. This means that ignorance is NOT an
excuse.
- At no time shall a user or IRCop share, transfer or give away pornography
that deals with subjects who are not past the age of 18. This network
will immediately remove anyone found dealing in “child pornography”
and will seek to make the law enforcement agencies aware of this users
information and activities.
Section 1 Approval & Appointment Of IRCops:
- IRCops are appointed at the discretion of the respective Server
Administrator .
- The Network Administrator would like to remind you that you should
only appoint users to the position of IRCop, if you, the Server
Admin knows and trusts the user to be appointed. .The actions of
your opers reflect directly on you. Violations of our terms of service
by your opers may result in a de-link.
- No O:line is to be added to any server without approval from
a TechAdmin or Netadmin.. The Net Admins and Tech Admins reserve
the right to decline the appointment of any IRCop on any server
- All Global and Local Operators are required to be present in
and help users in Awesomechat’s official help channel #Help.
Any Global or local found not in this channel will be disciplined
Section 2. Qualifications:
Becoming an IRCop requires a strong working knowledge of IRC and
this IRC network. IRCops must have a good working relationship with
their server admin(s) and other IRCops. IRCops are selected when there
is a need. IRCops are encouraged to seek training and guidance with
learning so that they may further their own knowledge and opportunities.
- All new IRCOps will begin as a local-op until such time as their
Server Admin has determined that the IRCop has the required knowledge,
skills, and can handle the responsibilities of the next level. When
this plateau has been reached, either the Admin or the Local-Oper
shall arrange with a Tech Admin to be tested for the position of
Global Operator. Upon the local earning a passing score on this
test, the Admin of the local shall be notified and it shall be that
Admins responsibility to promote the Oper from local to global.
Only a Tech Admin or above can test global applicants.
- IRC ops should seek out training from their own Server Admin.
These Server Admin’s and Co-Admin’s shall make every
effort to ensure their staff is well trained. In the event the Server
Admin or Co-Admin is unavailable, the Operator(s) should seek out
a Tech Admin for training until such time as their training can
be resumed by the Server Admin.
- This network does not allow for staff to be taken from other
servers without the consent of the Admins involved and the Tech
Admin Staff. If an oper wishes to switch servers, this must be ok’ed
through the chain of command as listed above.
Section 3. IRCop Responsibilities:
- Ensure you have the necessary knowledge to be a good and useful
IRCop.
- Reconnect servers to your best abilities if one should split
off the Network, or in a Net Split. It is the responsibility of
ALL Opers to ensure that any server or servers which have split
are reconnected as quickly and efficiently as possible. Failure
to reconnect servers can result in a demotion or removal of your
O-line.
- To enforce the rules of your server as decided by your Server
Admin, and to enforce the Network Rules as per this charter (Article
[2]).
- To use sound and rational judgement when dealing with the users
and problems arising from the daily running of this network.
- To properly help a user who requests help with the Network related
problems.
- An Oper will not abuse their position and power to use Operserv
& IRCops features of Chanserv to make your self an op in a channel
that you do not have access to as an op, unless approved by the
channel founder.
- Channels are independent of the network. Channels belong
exclusively to their founding member(s).
- ‘Spam’ and ‘advertising’ unless covered
within the Network Rules are channel issues. The sending of
malicious content via a file or a URL is to be considered a
Network issue.
- An IRCOp will not to Kick, Kill, Gline or Shun for vanity reasons.
Glines by Regular IRCops are good for 2 days. If a user needs for
whatever reason needs a permanent Gline, a member of the network
staff (CSop, Services Admin, Techadmin Netadmin) must be contacted
with this request and valid reasons must be shown. If a Tech-Admin
finds an improperly placed GLine, it WILL be removed without warning.
- IRCops should take care when involved in internal channel disputes.
This network maintains a distinction between Channel and Network
issues. An IRCop should not become involved in a Channel issue unless
specifically asked to do so by the channel owners/operators. This
should occur only after every effort by the channel opers has been
made to resolve the issue(s)
- IRCops are strongly encouraged to mark their nick appropriately
when away from the keyboard so that other IRCops and users are aware
of your status.
Section 4. IRCops Rights:
- IRCops have the same rights as any user, along with the rights
of fair treatment when called to account for utilising their IRCop
powers.
- To request a TechAdmin to look into removing a gline.
- To request his/her Server Admin or Network Staff IRCop to look
into a fellow IRCop or Admin's actions.
- To have Chanserv access in #OpersRock the official Oper/Admin
channel.
- To deny access to any user to their respected server if such
user poses a real threat to that server or to the network.
- When asked about personal information the decision to reply is
your choice but said reply should not be rude or abusive.
Section 5. Chain of Command:
All IRCops should realize that other IRCops do have functions to
perform that are not always visible. It is not always convenient to
drop whatever one is doing to answer or solve issues that could have
been dealt with further down the hierarchal tree. Because all functions
and duties of some IRCops are not visible, they should be treated
with the respect if assistance is asked for at a time they are otherwise
dealing with network business. Remember that all IRCops are human
and if you are found disrespecting them, the chances of them wanting
to help you is very slim. It is a matter of treat your fellow Opers
and Admins as you wish them to treat you.
IRCops should follow the chain of command for problems or supervision
in accordance with the accepted hierarchal structure, and as per Appendix
A at all times. If you are found breaking the chain of command, you
will be at least warned and if it occurs more than once you risk further
action. The chain of command is there for a reason and following it
is essential for a quick resolution to a problem.
Unless it’s a network related issue that is urgent there is
no excuse for taking a problem beyond your server admin.
Possible consequences for misbehavior are initially decided by the
appropriate server admin alone, or in conjunction with the Network Administration.
Consequences will be proportional and relevant to the offence, and may
include:
- Temporary suspension of O:line
- Demotion to a local O:line for a probationary period.
- Removal of Services Admin or CSOP access.
- Refusal to future O:line opportunities
- Removal from the Network
AwesomeChat is committed to facilitating the supervisory relationship
between Server Admins and their IRCops. Every effort should be made
to resolve problems at that level first. If the problem remains unresolved
after the Admin has investigated and made a decision, a member of the
Network Administration should be approached with any and all supporting
documentation.
A server admin is an integral part of the network and the Admin has
a lot of responsibility in maintaining the reputation of their own server
and in the network.
Maintain the server in good working order.
The Server Admin must notify the TechAdmins, who will in turn inform
all the necessary people of the request for new ircops.
The rules listed in Article 4 section 3 subsection 1 apply to any
additions of staff.
Section 1. Server Rules:
The right to create specific rules and regulations for IRCops on
their own server. Said rules and regulations must comply with the
Network charter. In the event of a conflict between Server rules and
Network Rules, the Network rules shall be followed.
Section 2. Server Staffing:
The Server Admin can appoint IRCops subject to Article [4] Approval
Of IRCops, and the limitations if a server on test as per Article
[11] Servers Approved for Test-Link to a maximum number of:
1 Admin
1 CoAdmin
6 Opers (Locals / Global)
When appointing IRCops the Admin accepts responsibility for his/her
IRCops, their actions, and to ensure they have the necessary training.
Section 3. Server Shell Access:
With the exception of Article [10] Server Linking Requirements Server
Admins may give shell access to whomever they like.
However the Network recommends that for the safety and security of
both the Network and the Servers on the Network, that Admins be very
cautious about giving out their passwords. The Tech Admin’s
will NEVER give out a server password.
Any Admin or Co-Admin that changes a shell password must notify the
TechAdmins A.S.A.P. either in person, via email, or memo of the new
password. Memo is the preferred method so that the Tech Admins can
be made aware of the change and can edit their lists accordingly.
Network staff (CSops, Services Admins, & TechAdmins) are appointed
solely at the discretion of the Network Admins.
These members, to varying degrees dependant upon their position, have
delegated network authority from the Network Admins. They are responsible
for ensuring the smooth and continuous running of the network, including
approved policies, linking new servers, arranging training and looking
after the other various administrative and technical issues relating
to this network.
- The overall responsibility for management of AwesomeChat is with
the Network Admins. There are 3 NetAdmins of which 2 are founding
members of the AwesomeChat Network.
- NetAdmins have final say on all network policies and procedures;
oversee the organization and operation of AwesomeChat with total discretionary
powers to insure that AwesomeChat is run in a manor that conforms
to their desires and expectations.
- Network staff (CSops, Services Admins, & TechAdmins) are appointed
solely at the discretion of the Network Admins.
- All servers must have a multi-backbone T1 or better to be considered
for linking.
- All servers must have the following available ports: 6667-7000
+ 7777
- Every server must have a static IP address (one that does not change).
- UNIX OS's or *NIX OS’s only. No wIRCD's (Windows based IRCD’s)
will be permitted.
- The AwesomeChat NetAdmins and TechAdmins must have shell access
to all linked servers so that in an admin's absence, O:lines, C/Nlines,
and other lines can be changed in an emergency situation.
- All servers must have backup O:lines for NetAdmins and TechAdmins.
- Most servers will be compiled as a hub, and must be able to function
as one if needed.
- No link will be approved for a server that intends to run two IRCD
processes at the same time, when those processes will be connected
to different networks.
- The test-link with all new servers will last for a period of no
less than fourteen days. During this period server connection lines
will be restricted. Please do not ask when your server will become
a permanent link.
- During test link period no olines may be set in your conf file
except for the Servers Admin unless approved by the AwesomeChat Network
Administrators.
- After the test link period and approval given for a permanent link,
o:lines may be added as per Article [4] Local & Global IRCops:
Sections 1 & 2.
- Unless agreed with by the NetAdmins no o:line may consist of all
wild cards: (*@*.*) The minimum requirement is: *@*.domain.com. Any
Oline found to be in violation of this rule will either be fixed or
removed.
AwesomeChat understands people may from time to time delink. We would
appreciate as much prior notice as possible, no matter what the reasons.
The network administration will not be upset with any server admin if
he/she needs/wants to take their server down. We would rather he or
she leaves on a positive note!
Note: This document dated March 3, 2006 supersedes all previous documentation
relating to AwesomeChat Network Rules and Policies.
AwesomeChat Network ™
Copyright © 2001 – 2006
All Rights Reserved ®Appendix A
Appendix A
|
  |
