Introduction
IRC is a wonderful medium for communicating with folks from all over the world. As nice as this is, there will always be those who want to ruin other people's fun. They do this by:
1. Harassing/Stalking
Following someone around, talking to them when they have been repeatedly told that they don't wish to be bothered.
2. Flooding
Sending massive quantities of text to a channel or to a person in private message. This is not only abuse, but it puts an unnecessary load on our servers and services.
3. Cloning
Having more than one client up from the same ISP connection. These are many times used maliciously to flood the network or channel (flood-bots), or simply to use of all the server connections so nobody else can join
4. Services Abuse
Services abuse includes, but is not limited to...
· Registering an unreasonable amount of nicknames and/or channels.
· Flooding services with mass quantities of services requests (ie. having a script that ops you with services when you're de-opped and being deopped by someone else's script over and over.)
· Filling someone's memo box with mass quantities of harassing memos.
· Registering a newbie's nickname just to "ghost" them.
5. Channel Takeovers
Services has made it almost impossible to take over channels for the long term, but people still try. Newbies give their password to folks who claim to be damage-irc staffs, and these passwords are used to steal the channel registrations.
Note:
No damage-irc staffs will ever approach you out of the blue and ask you for your password for any reason. If anyone ever does this, contact an IRC Operator immediately and let them know.
6. Impersonating damage-irc Staff
If you present yourself as an IRC Operator, and you aren't, that is impersonating staff. As a matter of fact, if you present yourself as affiliated with damage-irc at all and you're not it's "impersonation"
7. Impersonating Services
Taking a nickname like NickServ or ChanServ is impersonating services. If you get a message from anyone with these nicknames please report them to an IRC Operator.
8. Hacking an O:line
This is the attempt to become an IRC Operator on a server on which you don't have an O:line. This can be either a malicious repeated attack, or it can be a badly configured script which opers someone everywhere, not just the server or network they have an O:line on.
The first time we see this, you'll generally be warned (unless the /oper commands are coming in rapid succession) and you'll be given the opportunity to stop or fix your script. If it happens again, more stringent measures will be taken.
In the case of abuse certain actions will be taken. The person who is abusing will usually be spoken to. If speaking does not help the situation, some or more of the following actions may be taken:
1. Kill
This is a forced disconnection from the network. This is used in the case of flooding to stop the flood, or to get someone's attention.
2. K:Line
This is a server specific ban placed on a single server. If you are banned from a single server, you need to contact the server admin with regards to how to get the K:line lifted if possible.
Note:
An individual admin can set a K:line on his/her own server at any time and for any reason or no reason at all. If you fail with negotiating with the individual admin, there is nobody higher to appeal to. The good news is, there are other servers on damage-irc that will probably be open.
3. Auto Kill (AKill)
This is a network-wide ban usually lasting a fixed duration. This is caused by repeated, unrepentant abuse. Sometimes the auto kills are set wide enough to catch a lot of innocent people (sometimes whole ISPs). In these cases, we need the help of the ISP in quesiton to discipline the user, or cancel their account so that the abuse will stop.
If you are caught in an auto kill, you can send email to kline [at] damage-irc [dot] net and explain the situation. Be sure to include whatever message you got from the server when you were banned. We will work with you to try and get the situation resolved.
4. Services Ignore
When services are abused, one can be put on services ignore. This means that you can't use services. It won't op you, you can't register channels or anything else having to do with services. This is usually for a fixed duration.
5. Frozen/Suspended/Closed/Forbidden
When you abuse in any kind, an IRC Operator will first mark your nick and take further action such as freeze/suspend/close/forbid your nick/channel.
If this happen to you, please contact our damage-irc respectively team such
as MassAds Team, OperHelp Team, Closures Team and Kline Team or for higher appeal goes to the Executive Board.
The above mentioned information is just the a common policy and network response. I include more information about network policies below which is written by me and some other team leaders.
Admin/IRCop/Team Policy
Server Admins (Admins).
Admin responsibilities include:
1. Keeping up-to-date on damage-irc policies, procedures and activities.
2. Keeping damage-irc administration as a whole informed of any prolonged absences.
3. Appointing a representative to fulfill his or her duties when necessary, and informing the damage-irc administration as a whole of the appointment.
4. Informing the Damage-IRC administration as a whole of any changes in a timely fashion.
5. All IRC Operator responsibilities.
6. Direct supervision and responsibility for their IRC Operators.
7. Appointing IRC Operators who can be trusted to act in the best interests of the server and of damage-irc as a whole.
Admins will not:
1. Move the server netwise or physically to a location generally regarded as inferior, except as a temporary or emergency measure, as decided by the EB.
2. Drastically alter the location of the server netwise or physically.
3. Link a server which has not been officially accepted by the damage-irc administration. An exception can be made in the case of emergency, testing, or training situations with the approval of the SM (Services Master). These exceptions are not to last more than thirty days, after which time a review of the situation is required by the EB.
IRC Operators - Server Team Staff (IRCops).
A Damage-IRC Operator assists the Admin in server maintenance as assigned and helps maintain network stability. IRCops assist users in becoming oriented to the damage-irc IRC Network, Auspice Services and in the mediation of disputes. IRCops offer assistance in resolving conflict and work with other administrative staff to maintain a safe environment.
Specialized Teams.
The following teams have been empowered by damage-irc's Executive Board to function within the scope of their team policies and procedures as presented to the EB.
damage-irc's SM (Services Master) and Executive Board provide general administrative support to the network and it's staff. Team Leaders, have the authority to make policy and staffing decisions regarding the team and it's operations. Complaints about a team, it's policies or it's staff, may be submitted to me as webmaster. Only in an Emergency Situation, will a member of the EB or the SM overrule the decision or policy of a Team Leader.
Teams' Policies:
OperHelp Policy
OperHelp Team is an important team in the network. They are very busy person. Please be considerate. Below are some guidelines:
You can look up for a password a day.
OperHelp Team need at least 1 week to respond for password issues.
OperHelp Team need at least 2 weeks to respond for take over issues.
No idling in #OperHelp.
You will be voice accordingly in order you join #OperHelp.
If there is no IRCop online, email ircop [at] damage-irc [dot] net
Closures Policy
The damage-irc Closures Team reserve the rights to suspend/freeze/close/forbid any channel for any reason which lead to abuse. When a channel is closed, an email containing information of closures such as channel, founder's nick, reason and etc must send to the EB board and the Abuse Team. Any IRCop can unsuspend/unfreeze/reopen/unforbid any nick/channel with the condition the IRCop send an email regarding the issues and must contain reason for reopen,when and etc. Include as much information as possible.
Channels that to be suspend/freeze/close/forbid:
War Channels - Closed Permanently.
Channels that are mass ads by the founder/aop/sop or any access user
Mkick and if repeated suspension will be needed according to situation. If repeated freeze the channel and deal with the founder.
Channels Impersonation - Closed Permanently.
Channels that are advertising other server - Closed Permanently.
Abuse Policy
Abuse Team is the main team to handle with the abusive users and IRCops. One is consider abuse in one of the conditions mentioned below:
Harrasing/harm user.
Flood/Clone/Hack/Nuke
Mass Ads (servers,website)
Virus/Worm/Backdoor DCC
Services Abuse/Flood
Channel/Nick Impersonation
Note: More condition will be included till the team leader send a full list for me.
FloodHelp Policy
FloodHelp Team is assign to control the flood and clone in the network. Cloning can be described as the connection of multiple clients from a single IP Address or Host. Cloning can cause many problems to networks, and are generally used in the flooding of a channel and causing various network harm. It is for this reason that we have decided it necessary to limit the number of connections allowed from a certain user. Flooding is when you type many lines at a short time. Those people who flood channels/private messages/services cause many problems to the network. Due to this, we have taken actions to ban any user caught flooding from the damage-irc IRC Network and akill them from the network. Below are some guidelines you must follow:
One IP can connect to the maximum of 9 users with different nick but not flooding nick. In this case flooding nick means Nick1, Nick2, Nick3
If you are an owner of a cybercafé or a cybercafé customer and happen to experience AKILL/KLINE, please contact the EB and registered as a exploit. So that FloodHelp Team wont AKILL/KLINE when an IP from many connection is connecting to the network.
Clone is not tolerated whether to make loads of that channel.
MassAds Policy
MassAds Team is responsible for anti-inviting in the network. Inviting means inviting server,website or channels. Advertising is basically any message sent to a channel or user asking them to check out a web site or server or to join another channel on the network. Some channels may allow advertising on their channel in channel messages. This is NOT encouraged, however we tend to "look the other way" in these cases, rather than interfere in channel policy. Mass advertising in the network will result you to, at the minimum AKill for a day or two. If the same IP is caught for mass advertising again, permanent AKill will be added for the IP.
Note: More guidelines will be added till the team leader send it to me.
Security Policy
Security Team is setup to guide the users for security purpose. Besides that, this team also provide information about the latest virus, worm and backdoor. This team will also restrict some IRC Scripts that cannot be use in the network because of war purpose.
Note: More guidelines will be added till the team leader send it to me.
Kline Policy
This is the leader of the teams. Several teams is under Kline Team. More information will be provided soon.
Technical Policy
Technical Team is assign for to keep the network setting in correct order. This is also a help team. IRCd commands and Services commands can be ask. They update the latest version of IRCd and Services.
Complaint Policy
The procedure for registering a complaint about an IRC Operator or Admin is:
Drop by #Abuse and voice out your problem to the Abuse Team
Try to resolve the problem by talking to the IRC Operator or Admin directly.
If there is still a problem, report it to the Admin on whose server he or she has an O: line. In the case of an Operator with more than one O: line, try to report to the Admin of the server the Operator was oper'd on at the time of the event, if possible.
If the problem remains unresolved after the Admin has investigated and made a decision, a report can be sent to the EB with supporting documentation.
Linking & Delinking Policy
Linking a server to damage-irc must run the ircd version approved by the Technical Administrator. Information about the ircd version used by damage-irc servers can be found in #Technical. A server may be delinked by a majority vote of the Executive Board. If the Executive Board votes in favor of delinking, all damage-irc servers shall remove C/N lines within 7 days. If the Executive Board votes against the removal of the server the following will happen:
Any actions stated in the vote are to be put into effect immediately.
The server should then have a probationary period of 60 days from the closing of the vote, or from the time it re-links to the network.
At the end of the probationary period, another vote can be requested if another Admin feels the server/Admin did not fulfill the duties necessary of a damage-irc server and Admin.
A server may be temporarily delinked (juped) if it shows considerable disruption to the rest of the network, such as failure to update the ircd files in a timely manner. This action should be no longer than 5 days. Otherwise, it qualifies for delink.
AUP - Acceptable Use Policy
The Acceptable Use Policy governs the use of computers and servers on the damage-irc Internet Relay Chat Network, including but not limited to, its chat forums, web pages, and e-mail services. As a user of these resources, you are responsible for reading and understanding this document. This document protects the users of damage-irc, computing hardware and networks, and system administrators. Connection to the damage-irc IRC network is a privilege, not a right. damage-irc reserves the right to deny access to its network without advanced warning and without being under any obligation to provide a reason. Where a reason is provided, it is done so at the discretion of damage-irc. damage-irc is an unmoderated forum made possible by the donations of its service providers and volunteer staff. By connecting to damage-irc you have accept that you are a guest on a private system. Your privilege of use is revocable at any time for any reason. Further you accept that you have no claim to any data maintained by damage-irc that you have used. damage-irc does not control/monitor the content transmitted via its services and, as such, does not guarantee the accuracy, integrity or quality of such content. You understand that by using damage-irc may be exposed to content that is offensive, indecent or objectionable. Under no circumstances will damage-irc be liable in any way for any content, including, but not limited to, for any errors or omissions in any content, or for any loss or damage of any kind incurred as a result of the use of any content posted, emailed, transmitted or otherwise made available via damage-irc. damage-irc reserves the right to alter this AUP and any terms and conditions of service at any time without prior notice. However, a notice will be posted in the web at least 10 days in advance of such changes if possible. Notice is deemed given when sent.The damage-irc AUP is under constant review. We consider comments from our users and from experienced staff. We will change this document from time to time. You are subject to the AUP in effect at the time you use any damage-irc resource/service, and to each revision of the AUP that becomes effective subsequently. This version of the damage-irc AUP supersedes all earlier versions.
The formation, construction, and performance of the AUP will be construed in accordance with the laws
of Malaysia. If any provision of the AUP is held invalid or unenforceable, the remainder of the AUP will
nevertheless remain in full force and effect. If any provision is held invalid or unenforceable with respect
to particular circumstances, it will nevertheless remain in full force and effect in all other circumstances.