FORMS:

TEST LINK EMAIL TO APPLICANT:

[YOUR SERVER]
When you compile your server, you need to use version 5.3.01 of the ChatNet IRCD. Please compile your server as a leaf, and with the ability to hold at least 1024 clients. Never compile a server on ChatNet with reliable clock. It does not matter if you run a NTP protocol or not. You need to allow the services to maintain the network timestamp or there will be a serious desync in the network and your server will be Jupitered. If your server can not maintain its uptime from day 1 of your test link, we will delink it with out warning. The ChatNet Routing Committee will be running audits of server performance twice a year. If during this audit, your server is flagged as not helping to improve ChatNet due to its performance, this server can and will be delinked. We are only reviewing the server. The staff is not a CRC issue.

[IRC OPERATIONS]
You may only add the people that are listed on your application as IRC Operators during your Test Link. Which in this case is [Enter Number of operators on AP.]. Please do not add-back up O:lines for current IRC opers and administrators. You will be added as user level 500 in Nuthouse and your staff will be added as level 200 throughout the Test link.

[DNS]
The server will be linked as [***ENTER-NEW-SERVER-NAME***]. This is the name we will define in the M:line. We will not make a DNS entry right away. The first part of the linking process is to test stability of the link. It is not beneficial to a user to join a server that is constantly delinking due to communication failure.

[Mailing Lists]
You will be added to the mailing lists when your server has completed its [***NUMBER-OF-DAYS-FOR- TEST-LINK***] day test link. You will be added to a mailing list CADMIN that is currently in place. This list will help us inform the test link servers of crucial updates and items such as important policy changes. When your test link is complete you will be added to the following ChatNet mailing lists:

ADMIN - ChatNet Administration ONLY
CADMIN - ChatNet Administration, Committees, Generic Information
OPERS - ChatNet IRC Operations
Your IRC Operations staff will be added to OPERS only.

[Network Layout]
Some simple rules you should know before you bring your server online. As you are the liason for the server to the network, it is your responsibility to inform your staff of the rules of the network. It is imperative that you communicate these rules to each member of your staff!

1. ChatNet exists for the enjoyment and entertainment of the users.
2. Users cannot be killed or GLINED for expressing their personal opinions, or ideas.
3. Any GLINE or KILL messages should be professional. 
4. #ChatNet is the official network help channel. Idling in #chatNet is strictly prohibited. If you do idle there, you may be kicked or banned by other staff. 
5. Personal disputes are not to be displayed in channel. If you have a problem with another member of the staff, take it to private message or private email.
6. You are allowed four global irc operators. The Administrative staff is included in this count. If you have an Admin and Co-Admin with global O:lines, then you can only have two more globals. You may add as many local operators as you feel are neccesary for the smooth operation of your server.
7. ChatNet allows each IP/host to have 20 clones. If any host goes over this amount, they may be killed or glined, preferably with a message explaining why they were glined and to visit http://routing.chatnet.org/clone.html
8. WinGates are not allowed on ChatNet unless they are SECURE. Any gate being found to be unsecure may be GLINED for 14d. 
9. It is suggested that if you have to GLINE a dialup host, that the GLINE last for a max of 1 hour. 
10. Use your head. Common sense is the most important tool we have. If you have a question on how to handle any situation, get a second opinion. Do not hesitate to ask another admin or operator for their assitance.

K9 is the official and only channel service on ChatNet. Any K9 related issues should be sent to #doghouse, or to a CService representative. IRCops are not to interfere with the day to day operations of CService. CService has its own level added into ChatWorld so the members can see OPMSG's and get information on channels. It is common for CService members to ask global operators to "spew" a host so they can see if a person asking to get addmasked on K9 is on an internet cafe or whatnot.

Gate Scanning Bots - The ChatNet IRCD has the ability to scan incoming connections for unsecured proxy servers. Many users will see this as a DoS  attack. You should state that you are scanning in your MOTD as well as your REMOTE.MOTD. This will be of great assistance when questions are asked regarding port scans. If you are not using the internal IRCD GateScan, you have the option to use a bot running as a Local Operator on your server. These bots should have a LOCAL o:line on the  server. Under no circumstances will an Automaton other than Operator or Channel Services have a global O:Line on ChatNet. 

NickServ/MemoServ - ChatNet does not have any kind of nick registration service or memo service.

[V:LINES]
A V:Line is a vanity line. It is a form of host masking that is connection specific. Although ChatNet actively uses Host masking (mode +x), there are servers online that have not migrated to the current IRCD and are there for a liability to user security. This is being rectified as quickly as possible. there are very few rules governing Vanity lines. Most administrators give a Vanity line to persons that they know.  Vanity lines should not be offensive in nature. If you choose to give out Vanity lines, do not give Vanity lines to users with your server or the network name in them, i.e. user@Your.Server.US.ChatNet.Org or user@anything.ChatNet.Org. These host addresses are reserved for the ChatNet staff. Because of this, they are easily exploitable.

[Network Structure]
Currently, the hierarchy of ChatNet is built like this:

• Executive Council: This council is appointed by Nu Tech Software Inc., whom sponsors ChatNet's DNS and K9/hosting services. This council currently consists of BP, Dr-Who, pHaNtAsY, LabattZ, and MrMud. The Executive Council (EC) governs all officials.
• Admins/Co-Admins: A Co-Admin has the same status as an Admin. They answer directly to the EC. Routing: They answer to the Admins. This group is in charge of approving new servers for link on the network.
• Global Operators: They answer to their respective admins, other admins, and the EC.
• Local Operators: They answer to their respective admins.
• CService: They are responsible for channel registrations, and K9 operations. They answer directly to the EC.\

[Abuse]
Any issues of abuse are handled directly by the EC. If an issue of abuse is brought up against an Admin or IRCop, it is investigated by the EC and they will rule on it. The abuse system works on a three strike way, unless an offense is grounds for immediate dismissal. Once an official is removed for abuse, they cannot serve in an official capacity again.

[Fun things]
You are allowed to use /wallops for fun and playing, but you must keep it clean and non-offensive. Killing other operators is also acceptable for fun, but if they ask you to stop then you should.

[#Nuthouse]
This is a hangout room for Admins/Opers/Users. While users are welcomed to participate in chat here, they can still be kicked or banned for misbehaving. If a user wanders in asking for help, it is encouraged that you help them, even though it is not an official help channel.

[#Chatnet]
This is the official help channel for the network. Idling here is not allowed by staff or users. If you or your staff idle here, they may be kicked by other ChatNet staff. Currently, any global operators that are opered up are required to help here. Admins, and local operators are exempt.

[Routing]
The rules regarding the ChatNet Routing commitee are found at http://routing.chatnet.org/policy.html

This document is designed to guide you and your staff to the way of smooth operations of your server and the network as a whole. As stated before, it is imperative that you communicate these guidelines and policies to your server staff. If you have any questions, please feel free to contact us at routing@chatnet.org, come to irc.chatnet.org and join #routing, or contact your routing member in charge of your link. If you are ready to link your server, please join irc.chatnet.org and see either myself, [ENTER YOUR NICK], or [ROUTING-BACKUP NICK]. We hope you enjoy your time on ChatNet, and wish you and your server a long and great relationship here.

Please join the irc.chatnet.org and see either me, [ENTER YOUR NICK] or [ROUTING-BACKUP NICK]. Your C and N lines need to be added to the uplink servers yet.

[INSERT SIGNATURE]

SERVER Submission to CADMIN

[SERVER_NAME - IP]
1: ADMINISTRATORS
   a: Name:
   b: Email:
   c: Phone:

2: LOCATION
   a: City/State:
   b: Country:

3: ROUTING
    a: Uplink:
    b: Connectivity:
   c: Routing Member in Charge of Link:
   d: Routing's reasons for linking the server:

4: STAFF
Nick - Name - Email

[INSERT SIGNATURE]

SERVER REJECTION

This is in regard to your server test link. After reviewing your servers performance, we have come to the conclusion that this server does not meet the standards requested by the ChatNet Administration in regards to the following:

[INSERT SIGNATURE]

SERVER SUBMISSION TO CADMIN

I: The ADMIN - [ADMIN(s)]
   A: How are the server ADMIN(s):
    B: Do you have any problems with the ADMIN(s)

II: The Staff
   A: What is your opinion about [OPER1]:
   B: What is your opinion about [OPER2]:
   C: What is your opinion about [OPER3]:

III: The Server
    A: How is the server's over all performance (UPTIME)
    B: How is the server's connectivity
    C: If there is something about the SERVER that you find lacking please specify:
    D: Has this server made any positive impact on ChatNet?
    E: Do you see ChatNet benefitting from permanently linking this server?

BBN Planet Back Bone Structure -- If they are connected via BBN, we need to get traceroutes from both directions. BBN was one of the first Internet Network providors, and they haven't improved in years. Even Chelmsford has finally dropped BBn and they were die hard supporters.

C&W Back Bone Structure
US:
NORTH AMERICA BACKBONE -- Traffic Report
International History