Network Policy
Introduction
These Policies govern the use of computers and servers on the KDFSnet 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 KDFSnet, computing hardware and networks, and system administrators.
Connection to the KDFSnet IRC network is a privilege, not a right. KDFSnet 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 KDFSnet.
KDFSnet is an unmoderated forum made possible by the donations of its service providers and volunteer staff. By connecting to KDFSnet you accept that you are a guest on a private system. Your privilege of use is revokable at any time for any reason. Further you accept that you have no claim to any data maintained by KDFSnet that you have used. KDFSnet 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 KDFSnet, you may be exposed to content that is offensive, indecent or objectionable. Under no circumstances will KDFSnet 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 KDFSnet.
KDFSnet 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 sent to the kdfs@kdfs.net mailing list at least 10 days in advance of such changes if possible. Notice is deemed given when sent.
About KDFSnet
KDFSnet was initially created by Kilmarac in the year 2000 when he, some of his friends, and a significant portion of a roleplaying group he was involved in were banned from another network without warning, and for no apparent reason. The network started as just a safe place where the group could roleplay and have fun without interference. Since then it has opened its doors to the public to use, and has grown into a full IRC network.
Overall Philosophy
We have founded the KDFSnet IRC Network in order to provide a place where people can chat and have fun in a stable environment. Where the users can have control over their own channels. Where the rules are kept to a minimum and based off of common sense. Above all, where everyone can call it a place to have fun.
Operations of The Network
The overall authority on KDFSnet is the Command board. The Command board is comprised of the IRCadmin, and TechAdmins. The staff filling these positions can be found listed on the staff page.
KDFSnet will be governed day to day by a number of teams: Admins, Help, Services, and Web.
The Command Board will appoint team leaders for each of these teams. The team leaders will report to the Command Board, with the exception of the Admin Team. All members of the CB will be subscribed to the admin list and mostly communicate with the admins (the CB are team leaders for the Admin Team).
Almost all policy issues will be dealt with by the Command Board. The Command board keeps the admins informed, and in many cases will ask for an Admin Vote on issues.
The KDFSnet Teams
KDFSnet operates its network in the team concept. Each team is given autonomous control over their areas of the network in the hopes that the admin team or the command board do not need to get involved in the operations of the network. They are expected to complete the tasks that fall to them in an efficient and professional manner.
Ideally each team will be headed up by an admin, however, the command board may appoint a non-admin staff member to a position if they feel that the person can handle the responsibilities of the position.
Team leaders select their staff by whatever method they see fit, informing the command board of any changes.
KDFSnet knows that there will be disagreements and butting heads. Admins will leave, servers will delink, people will quit the network. However, the command board should remain committed to keeping the network operational, and will always be there to assist in rebuilding the network. If the entire network quits against the command board, then it is only our own fault for not hearing what was being said to us before that occurred.
The downside of all this is that there really is very little "power" for a new admin. But people should decide what they are good at and volunteer for the relevant teams, then they can work their way up.
The leader and members of each team can be found on our staff list.
The Command Board
The CB has the last word on all aspects of network management.
The CB, however, is not in place to run the network itself. The CB expects each team to manage itself. Any member of staff who is unhappy with the management of the network should feel free to contact the CB either by mail or on the network itself.
The CB has the network’s best interests at heart and wishes for hard-working staff to be rewarded, and not have to use their ultimate power to resolve conflict.
The CB exists as effective team leaders for the Admin Team. Each team leader is free to run their team’s associated mailing lists as they see fit, however, the CB expects admins to conduct themselves professionally on the admin list. That means admins are expected to compose legible, non-abusive emails without excessive quoting. Failure to comply with this reasonable request will lead to the CB requesting the admin appoint a more polite acting admin to represent the server on the Admin Team.
The Web Team
Mailing List: web(at)kdfs.net
This team’s mailing list is open, to subscribe send an email to: with subscribe in the body of the email.
Responsibilities:
All aspects of the web site, including some form of template to be used on all official KDFSnet sites so they all look the same. That’s mainly so that anyone can fix up sites that work and look okay without having to wait a month expecting the Web Team to do it all for them.
Ensures smooth and efficient running of the DNS and mail for KDFSnet.
Updating DNS and answering emails for hostmaster(at)kdfs.net
Quickly responding to outages by altering the DNS pools.
Updating mail aliases and lists and answering postmaster(at)kdfs.net emails
If you have a problem with the website please send an email to ‘’’web(at)kdfs.net’’’
The Help Team
Mailing List: help(at)kdfs.net
There will always be a need for help from the users of the network. Whether this is because they are unsure as to how to do something, need help in registering their information, or because they have been auto-killed or k-lined from the network. In any case, the help team will be ready to assist them in their time of need.
Responsibilities:
Producing help documents.
Documenting standards of conduct for IRC Operators.
Training helpers.
Running #helpdesk, the only official help channel, which also includes helpers who aren’t IRC Operators.
Holding help sessions, when we have enough users to make it worthwhile.
Accepting abuse reports from users regarding staff, and making judgment calls on who should receive them.
The Services Team
This team looks after all aspects of services, including its maintenance and ongoing development.
Responsibilities:
Developing and maintaining our services package.
Deciding where services.kdfs.net should be and who should have what level of access to it.
Providing at least one download site where admins and other networks can find our software.
The Admin Team
This team is composed of all admins, co-admins and server representatives on the network. Any issue not strictly the business of any other team is dealt with by the Admin Team.
Mailing List: staff(at)kdfs.net
Responsibilities:
Training their IRC Operators.
Keeping track of what their IRC Operators are doing and dealing with misconduct accordingly.
Maintaining their ircd, e.g. upgrading it when there is a new release.
Promoting the network.
Upholding & updating network rules.
Any other business (by discussion and/or vote
Deciding if a test linked server becomes perm linked.
Other mailing lists
There are other informal mailing lists which do not correspond to any role on the network. Please see our site for more details.
Rules Of Conduct
For Users
You will not evade bans.
You will not mass advertise or mass invite.
You will not place bots on servers that do not allow bots.
You will not break clone limits.
You will not engage in denial of service attacks on users or network infrastructure.
You will not place Trojan clients (Sub7 bots, etc.) or other hostile bots on our network.
You will not allow bots under your control to break any of these rules.
We do not automatically monitor the content of conversation or file transfer in order to enforce these policies, however if we become aware of breaches of our policy then we will take action.
The above actions are subject to warning, /kill or /AKILL. Repetitive abuse will be reported to the Services Team and leads to possible nick or channel suspension/loss. Repetitive abuse will also be reported to the offender’s ISP.
Network staff will be there to help you, but if you abuse staff they may well /ignore you. Staff who are busy may direct you to #helpdesk.
For IRC Operators
All of the above rules for users apply to IRC Operators.
You will not interfere with channel management:
Flooders can be dealt with by channel ops.
Don’t use your o-line or services abilities to manipulate a channel unless you are doing so to prevent abuse (make sure you have logs to support such usage!)
If services are down and a channel owner requests ops, but you don’t know anyone who is on the access list then ask advice from fellow IRC Operators.
You are expected to help users and respond to polite requests for help:
If you are too busy, direct them to #helpdesk.
Make sure you are not invisible (umode +i) whilst opered.
You do not have to take abuse from users, but by the same token you may not at any point use your o-line or increased services access to exact revenge.
You are expected to take an active part in managing the network:
As a global IRC Operator you should familiarise yourself with the proper routing of servers, in order to help the network recover from splits.
You will behave professionally in network channels:
Our only network-owned channel is #helpdesk & #ircops (others may be founded in the future). In network-owned channels you will not abuse users in any way. Abusive users will be banned and you will be expected to /ignore them.
You will behave professionally on other networks
If it is brought to our attention that you have brought our network into disrepute by e.g. mass advertising us on another network, you may be subject to disciplinary action.
Keep your admin informed:
If you can’t fulfill your duties or be present on the network for an extended period of time, explain to your admin. This is not likely to pose a problem if the situation is temporary.
For Admins And Co-Admins
All of the above rules for IRC Operators and users apply to admins.
Manage your server staff:
Make sure they are trained.
Make sure they are doing their job.
Help them when they are unsure of what their duties are and/or how to do them.
Deal with any complaints regarding them before they turn into real problems for the network.
Comply with guidelines for adding IRC Operators.
Maintain your ircd
When the Coding Team releases a new version of the ircd you have one week to apply the change. If the upgrade is a major one (incompatible with previous versions) then expect your ircd to be juped until the upgrade is complete.
Promote the network:
Bring users, make us noticed, anyhow and anyway you can (besides spamming!)
Participate in votes:
New policy will be determined for the most part by vote of the admins. This includes linking of servers.
Keep your colleagues informed
If you are unable to attend the network temporarily, inform your staff and colleagues, and arrange for an acting admin to vote on your behalf.
If your server is not able to handle its normal client load for whatever reason, you are required to notify the Command board and expect it to be temporarily removed from the DNS pools so that it does not take clients. If your server is malfunctioning enough to seriously affect the rest of the network, expect it to be temporarily juped.
--------------------------------------------------------------------------------
Acceptable Use Policy (AUP)
Any nickname is valid on The KDFSnet IRC Network with the exception of nicks designed to trick users into believing you are part of the network or its staff, e.g. for the purposes of stealing passwords.
Any channel is valid on The KDFSnet IRC Network with the exception of those clearly founded to advertise other networks, or trick users into believing they are official network administration channels. If your channel moves from KDFSnet to another network, or you need to advertise another IRC network in your topic, we ask that you lock your channel +s so that its topic does not appear on a channel /list.
In enforcing the above policies we will use common sense. We will not take away someone’s channel the first time they put the address of an IRC server in it and we will not ban every "official looking" nickname. If you are in doubt, please the Help Team.
We do not monitor the content of conversation or file transfer. We also do not provide any guarantees that our servers will be available to you either for chatting or file transfer. We provide our services on a "best effort" basis, but be assured that we take that duty very seriously.
KDFSnet reserves the right to shut down any channel for any reason. We will attempt to make every effort to contact the channel owner to seek resolution to any problems we see before shutting the channel down, but this is not guaranteed.
Channel Founder status, or the granting of any level to a user in the channel will not be done by the network except in the case where the founder has emailed the network at help(at)kdfs.net requesting said actions.
Should you transfer the channel to anyone, KDFSnet is not responsible for recovering that channel.
The only channel member that the KDFS Network Staff will listen to regarding channel operations and hierarchy is the Owner/Founder.
*The only exception to network channel policies are found in the UCIP/KDFS operating agreement
Illegal Activity
KDFSnet strictly prohibits Illegal Activity of ANY kind, including but not limited to
The unauthorized transfer of copyrighted software, text, images, audio, video, or other material, also known as "warez".
The transfer of child Pornography.
Stalking.
Harming, or spreading files harmful to equipment owned by others, such as with a virus.
Conspiracy to commit a crime.
Providing a URL to a website that is involved with any of the above illegal activities.
Connecting Clients
KDFSnet reserves the right to scan all connecting clients for proxies such as HTTP, SOCKS or Wingate which are open and refuse or terminate the connection if detected.
KDFSnet reserves the right to perform additional types of scans or otherwise collection information about a connection, and refuse or terminate the connection based on the results.
Cost - KDFSnet provides all network services free of charge. There are no fees required to use any server linked to KDFSnet, or to register nicknames and/or channels. In return for the provision of free network access and services, we expect users to comply with the terms listed in this AUP.
Adult Channels
KDFSnet recognizes that it may have underage users on the network. Therefore the network requires the following
Channel names and topics are kept to a PG-13 acceptable level. If you must have topics or names that violate this, then you are required to set your channel to mode +s to hide it on the channel list.
Adult Channels have the following code at the beginning of their topic ADULT. This can be done by using CTRL+4 CTRL+B ADULT CTRL+B CTRL+4 when you create your topic.
Knowingly allowing or inviting minors into an adult channel will results in an immediate, irrevocable shutdown of the channel and banning of any users found to be engaged in such activities.
K-Line Policy
Violations
IRC is a great way to talk, have fun, and meet others with similar interests. However, as great as it may be, theres always a few bad apples. The following actions will get a response from the network directed against you.
Harassing/Stalking - Following someone around, talking to them when they have been repeatedly told that they don't wish to be bothered.
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.
Cloning - Having more than two clients 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. Households requiring more than two connections should submit a request via the helpdesk.
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.
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 KDFSnet staffers, and these passwords are used to steal the channel registrations. Note: No KDFSnet staffer 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.
Impersonating KDFSnet 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 KDFSnet at all and you're not it's "impersonation"
Impersonating Services - Taking a nickname like NickSrev or ChanSenv is impersonating services. If you get a message from anyone with these (or similar) nicknames please report them to an IRC Operator.
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.
Responses
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:
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.
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 KDFSnet that will probably be open.
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 question 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@kdfs.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.
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.
Network Operations
Admin Voting Policy
The Command board is expected to be able to agree on a course of action without a vote for the most part. An informal "show of hands" is not regarded as a full admin vote. Admins are expected to use common sense as a full admin vote can be a lengthy process.
As admins on this network, you are expected to participate in its running. If you are due to be away from the network temporarily (holiday/vacation/work trip etc.) then you must appoint an acting admin. This is usually your co-admin, but may be any individual who is not already serving as a member of staff on another server.
Neglecting to vote is a serious failing for you as an admin. Servers that persist in not voting WILL FACE A DELINK NO MATTER HOW MANY USERS THEY HAVE ON THEM OR WHO RUNS THEM. If you are not willing to help run the network, you do not belong here as an admin. Failure to vote may, at the discretion of the Command Board, lead to temporary loss of voting privilege.
Most votes and their discussions are to be carried out on the KDFSnet Public List, so that users are aware of what is going on. The vote may be held in private if the proponent so desires, but there should be good reason. If the vote is held in private, the proponent must still summarise the result to the public list after the vote is complete.
Currently votes are recorded by server admins emailing their votes to votes(at)kdfs.net. This email goes only to Harry and Colk, who are responsible for reminding admins to vote and the counting/announcing of vote results.
Managing O-lines
Home servers
Every IRC operator must have a "home server", and the admin of that server is responsible for the behaviour of the IRC operator no matter which KDFSnet server (s)he connects to.
Number of IRC operators
Each server may have O-lines for up to three distinct members of staff. This includes the admin and co-admin (if present), it does not include O-lines for proxy scanners or other programs that are approved by the command board for operation of the server or network. This figure will be increased as the network grows, and will be increased across the board.
Global operators
The Admin Team must be informed by email to staff(at)kdfs.net at least 48 hours prior to a local IRC operator being upgraded to global IRC operator. During this time, any objections will be made clear by members of the Admin Team and the promotion may be blocked by admin vote. When informing the Admin Team of planned oper promotions, it is preferable to do so before discussing the matter with the oper concerned.
The only way to become a global IRC operator is to serve for at least 30 days as a local IRC operator. Exceptions to this policy may be made at the discretion of the Admin Team, for example in the case of an existing or former global operator moving to a new server. An admin is under no obligation to upgrade a local IRC Operator to global in 30 days; that is completely up to the admin concerned.
Local operators
Admins may appoint local IRC operators with a view to training them until they are eventually suitable candidates for global O:lines. A user must have had a registered nickname for 30 days to be eligible for local IRC Operator status.
The Admin Team must be informed by email to staff(at)kdfs.net at least 48 hours prior to the addition of a local IRC operator so that any possible objections can be made clear. When informing the Admin Team of planned local oper additions, it is preferable to do so before discussing the matter with the user concerned.
Removal of operators
Admins may remove members of their staff at any time for any reason. They are required to notify the Admin Team of the removal but are not required to state reasoning.
Not all network staff have O-lines. Having IRC Operator status is not required before you can help in the various teams. Likewise, losing an O-line does not prevent you from continuing to serve in a team. Team composition is the business of the team leader.
Admins may be required to remove or restrict one of their staff member’s o-lines due to vote of Admin Team or order of the CB. Failure to promptly (24hrs) do so may lead to action against the admin concerned.
Backup operators
Each server may have as many backup O-lines as necessary. It is up to the admin of the server who they add backup O-lines for. It is suggested that admins are generous in giving out backup O-lines so that their server may be fixed ASAP should none of their regular staff be present. Backup O-lines for existing global operators may be added, removed or updated as the server’s admin sees fit without consulting anyone.
Notification
After any change of oper status (e.g. adding an oper, moving an oper to another server, promotion from local to global, etc.) a news item should be created which will send notification to the web site and public mailing list.
Link Procedure
The server link procedure is determined by the Admin Team.
Applicants are expected to fill in the link application form. No link will be given unless the form is filled in, and still must be approved by the Admin Team.
The Admin Team will inform the public user list when a new application has been submitted.
The Admin Team will spend up to one week investigating the link application and voting to decide whether the server will be granted a test link with KDFSnet. Voting on this matter will take place on the public mailing list. Justification for votes will be given where possible and any discussion, prior to voting, will also take place in public.
If they are unsure, the Admin Team may recommend that the server be linked to the test network first to assess its stability. The Admin Team may also request shell access to the applicant’s server to verify details of the link application.
A newly test-linked server will have one global O-line for its admin. All other O-lines must be local. In addition the admin will have no services access.
Admins or IRC Operators listed on the application who already have services access or full IRC Operator status on the network (e.g. they are existing staff who are moving servers) may retain this access unless majority decision of Admin Team decrees otherwise.
During a test link period, the admin may not add any new IRC Operators to their server.
Minimum length of test-link is 15 days. Test-link may be extended at the discretion of the Admin Team. When the Admin Team is satisfied that the test-link has lasted long enough, admins will either fail the test-link (and not offer a permanent link), or will accept the server for perm link to KDFSnet.
All perm links must be approved by majority admin vote.
Any server recommended to the Admin Team has shown promise from a routing aspect, and the Admin Team must assess actual performance of the server, and the character of the new admin, which is just as important. An Admin Team represantant will inform the applicant of the progress of their test-link (retarded/unreadable linkapp, accepted for test-link, denied test-link, failed test-link, accepted for perm-link) and copy the Admin Team on all correspondence.
Applicants denied or failing their test-link may reapply the same server after 30 days if they believe they have rectified any problems with their initial application. Alternatively, an application may be sent for a different server, but the "30-day rule" still applies.
Those listed as Admins and IRC Operators on applying servers must have a nick that has been registered on KDFSnet for at least 30 days.
This and other linking procedures may be altered on a case-by-case basis at the discretion of the Admin Team.
Delink Procedure
Any admin may call for the delink of another server by means of an admin vote. The server cited for delink may not vote. However, admins may not ABSTAIN on a delink vote.
Server routing
All global IRC Operators are expected to help with routing and recovering from network disruption. If server rerouting is required, an IRC Operator must first warn fellow staff:
/chatops I’m about to reroute neo, scream now if this is bad
(wait 10 seconds or so)
Then users due to be affected by the upcoming split MUST be warned via services global notice or a mass-notice:
/notice $neo.*KDFSnet.net users, the server you are using is shortly going to be rerouted to reduce lag. Please bear with us.
And finally the reroute takes place.
Please note that servers normally recover from netsplits themselves due to autoconnects defined in their configs. There should be no need to intervene unless there is a problem. For example, a server may be able to connect to its primary hub but packet loss on that link may be unacceptable, therefore requiring a reroute to its secondary hub.
Unnecessary rerouting of client servers is frowned upon - a few hundred milliseconds extra lag is not normally noticeable for users, unlike a netsplit.
The current optimal routing plan for the network is decided and documented by The Admin team.
Emergency Action
Any admin or services admin may take emergency action to immediately resolve or mitigate network problems. This includes actions that would normally require a full admin vote.
This can include immediate delink of servers or linking of new servers without the normal test-link procedure being followed.
The staff member is required to explain their actions in full to the Admin Team ASAP. Obviously, these actions should not be taken lightly and staff causing unnecessary damage to the network should expect to be reprimanded once the dust has settled.
Change Of Server Details
Admins are permitted to alter their server’s details such as operating system, hardware, and/or bandwidth. The Admin Team should be informed of any such changes.
Should a server need to move location net-wise from its current local network, then the server may need to reapply for a test-link period. This, of course, will be approved/denied at the discretion of the Routing Team.
The Admin Team must be informed by email to staff(at)kdfs.net at least 48 hours prior to the change of a server Admin so that any possible objections can be made clear. Should any objections not be resolved in discussion by the Admin Team then an admin vote will be called to decide whether the server should go through a new test link period, continue to be permanently linked with the new Admin or be delinked.
Nick And Channel Dispute Policy
Nicks and channels are registered on a first come, first served basis. In situations where the Admin team believes there to be a clear case of nick or channel stealing, services admins may intervene to settle the situation at their discretion. The decision of the Admin team is final.
Users wishing to report nick or channel "stealing" should do so via email to the help team. Please include as much information about the event as possible, including logs.
Users should note that such cases of nick or channel "stealing" can only occur through carelessness such as sharing passwords, accidentally pasting them to public channels or picking passwords that are trivial to guess. In a dispute, decisions over nick/channel ownership will be made by admins based only on information such as logs from services and what staff members have personally witnessed. As such there is no guarantee that a nick or channel will be returned to its original owner in these situations.
Users who persistently "lose" their nicks/channels are also unlikely to be taken seriously.
Adapted from various other network’s policies in the intrest of developing the best possible policy for this network. Current format and some wording follows the blitzed format of network documenting.