Organization, Principles, and Rules

Prelude to the Declaration of Principles of

Deepspace was formed out of the need for a group of friends to have a safe, stable, comfortable place to chat with others. Deepspace is uniquely different than other irc networks.We are a disability net that caters to the visually and hearing impaired. Our net is designed to accept and accommodate these users with special coding in our services and ircd's to allow for screen readers and special software used by our chatters. Deepspace promotes a good, wholesome chat environment where all users are made to feel welcome and not be harassed by other users. Deepspace highly regards all users and would like to convey the need for good conduct and courtesy.

Deepspace provides a family atmosphere, where ALL AGES are gladly received and can be assured of a pleasant chat environment. Deepspace is a FAMILY network. Please refrain from using illicit nicknames, channel names or channel topics. This includes, but is not limited to; any words, channels, or topics considered immoral, erotic, X-rated, pornographic, or sexual in nature. Deepspace does not condone or promote any obtrusive online activity that may be considered harassment of other users. Deepspace reserves the right to deny the use of any nickname, channel name or channel topic. If there are any questions then please ask any IRCop.

Deepspace does not censor its users' conversations, however, if the topic being discussed is unsuitable for minors then Deepspace asks that the discussions be held in private and not in an open channel. Please use private messages (/msg), queries (/query), DCC chats, or set the channel to invite only. Any complaints on this matter will be dealt with firmly. Structure:

Deepspace is a group of people who all have a prevailing interest in the prosperity of this network. All decisions affecting Deepspace as a whole are subject to review by the current members of Network Administration.

Network Founders:

The Network Administrators consist of five founders of the Deepspace Network and any others as they elect to the position. Deepspace Founders consist of: CHTANK, Johnc, Linz, Login, sahara, and PwcrLinux. The network founders have permanent, lifetime Network Administrator status unless they voluntarily resign from the position.

Network Administrators:

A council has been formed to make decisions and handle network business for Deepspace. This council, known as the Network Administrators, is formed of Administrators of servers that are currently linked to Deepspace. Decisions are made by majority vote. In order to overrule a previous decision made by the council, there must be unanimous agreement, with those Network Administrators in attendance for the meeting. The current Network Administrator's council consist of CHTANK, Johnc, Linz, Login, PwcrLinux, and sahara.

The chain of command is as follows:

  • Local and Global operators will contact their particular Server Administrator with any suggestions, concerns,or problems they have.
  • The Server Administrators will present these to the Network Administrators.
  • Any and all suggestions, concerns, or problems will be taken seriously and considered carefully by the Network Administrators.

NetAdmin Meetings:

NetAdmin meetings will be called as needed and will be announced by e-mail at least 48 hours in advance. Network Founders and Administrators will deem when a meeting is necessary. It is an open meeting and all are welcome to attend. All Server Administrators and their Co-Administrators are encouraged to attend the Network Administrator meetings. Associates will not be allowed to vote unless their Server Administrator is on the Network Administrator council, absent from the meeting and has made arrangements for the Server Co-Administrator to vote in his/her stead.

In order to conduct a lawful meeting there must be a majority of the council members in attendance. If, at any point during the meeting, the attendance is less than 51% then meeting continues but no voting will take place. Any motions made will be tabled until the next meeting.

Non-Network Administrator members in attendance to the Network Administrator meeting are asked to remain silent during the course of the meeting unless they ask the moderator, prior to meeting time, to address the floor. During old business, new business, and voting, the channel will be moderated in order to promote a more efficient meeting. After old business, new business, and voting, the channel will be unmoderated and open floor forum will be established where everyone in attendance has the opportunity to make suggestions, criticisms, announcements, gather information, ask about policies, etc. During open floor, Network matters only will be discussed.

Technical Administrators:

Technical Administrators are those who exhibit technical abilities and are familiar with coding. They are able to help set up services, code and configure ircds, answer technical questions, help server administrators, operators, and users. Technical Administrators are some of the real workers behind the scene making sure everything is in operational order. They are also part of the Administration and will assist in decision making. The Technical Administrator will also be a Services Administrator and therefore will have almost total control over services. They will; therefore, also be responsible to help maintain the services databases, such as akills, clones, sops, nickname, channel, and operdeny.

Server Administrators:

The Server Administrators of a server, also referred to as "the Admin", are allowed to appoint or otherwise select an individual to act as their assistant in their stead when they are not available. They must select someone who is already a global operator on Deepspace. This person will be the Server Co-Administrator and is also referred to as "the Co-Admin". The Server Administrators must actively participate in the operation of Deepspace. It is important to remember that you form the backbone of Deepspace, and therefore our users rely on you. Just as one depends on other Administrators, they too will need to be able to depend on you. If it is deemed that you can not, or will not, uphold the expectations laid out below, your position as a Server Administrator will be reviewed by the Deepspace Network Administration.

The responsibilities of a Server Administrator include, but are not limited to:

  1. Upkeep of their server's software, and upgrade of the software to the current version within reasonable time after the version's release.
  2. Security of their server and server configurations. This includes the Operating System if the Server Administrator owns the server.
  3. Keeping the server's configuration updated and consistent with Deepspace practices.
  4. Keeping themselves up-to-date with Deepspace policies, procedures and activities.
  5. Keeping Deepspace administration, as a whole, aware of any prolonged absences.
  6. Appointing a representative to fulfill his/her duties when necessary, and informing the Deepspace Administration, as a whole, of the appointment.
  7. Informing the Deepspace Administration, as a whole and in a timely fashion, of any changes to their server and server configurations. This includes link blocks, oper blocks, etc.
  8. Training, support and supervision of their Local Operators. Server Administrators are ultimately responsible for their Local operator's actions. It is therefore extremely important that Local Operator be chosen with care.
  9. Prior to assigning local oper to a user, please contact a NetAdmin in advance so we are aware of your selection. We can then give input as to whether we think they are ready for an oline as well. DO NOT ASSUME they will become a local oper until after speaking with a NetAdmin. If this isn't followed, your server admin status could be subject to removal.
  10. All responsibilities granted to Global Operators.

Server Administrator Rights:

A Server Administrator does have the right to:

  1. Add local oper block after approval from at least one NetAdmin.
  2. Remove any oper block they host.
  3. Deny access to their server from users who they deem to be abusive or disruptive.
  4. Change the numeric replies of their server, so long as they do not include profanity and are not offensive. The original meaning must still be conveyed in the new reply.
  5. Open as many additional ports as they feel appropriate.

A Server Administrator does NOT have the right to:

  1. Add any global oper block without the prior approval of the Deepspace Administration, except in the case of backup oper blocks.
  2. Link new servers without the prior approval of the Deepspace Administration. Even if the server has a link block on another server, approval is still required. This is to prevent inferior routing schemes from developing.
  3. Remove link blocks for servers they hub without the prior approval of the Deepspace Administration.
  4. Move their server, net-wise or physically, to a location that is generally regarded as inferior.

Server Administrator Duties:

Server Administrators and their staff (IRCops) will abide by all rules and policies of Deepspace.

Failure to discipline their representatives to advocate the well being of Deepspace will lead to their servers being disconnected. Server Administrators are responsible for making sure that their IRCops are properly trained. This including making sure that they get the proper manuals, making sure they attend classes offered, and testing by some means of their proficiency.

IRC Operators:

IRC operators, (IRCops), global opers, are the staff, or representatives, that protect the network from takeovers and disconnects. IRCops also provide help and assistance to users as well as maintain everyday operation. IRCops are expected to actively participate in the operation of Deepspace.

IRCops are determined by helpfulness, eagerness, promotion of the network, etc. To be considered for an IRCop you will be required to go through an interview and exam by the respective Server Administrator. Upon completion of requirements, that Server Administrator will deem if the person is qualified for the position. That nick will be brought before the Network Administrators and voted on for approval. Then the nick will be published for the Server Administrators and at such time, if there is a need, that person then is given the position of global operator to a primary server. Former opers who left Deepspace in good standing, upon their return, will be allowed to skip the normal process and let Network Administrators vote them back in as global opers. Also, after getting this position, any Server Administrator wishing to grant a backup o line on their server for this IRCop may do so.

The primary responsibility of an IRCop is to provide a safe and fun environment in which to chat. If a user requests assistance from an IRCop, the IRCop is obliged to help. If the IRCop feels they are unable to deal with the matter, for whatever reason, they must attempt to seek help from another IRCop.

An IRCop is essentially an ambassador of the network. This requires that they act in such a way that they reflect the ideas and beliefs of the network. It is important to remember that the only reason you are an IRCop is because Deepspace needs your assistance in running the network. Non-network issues will never require the use of IRCop privileges.

IRCop Rights:

An IRCop does have the right to:

  1. Remove an offensive or abusive user from the network with /kill. Deepspace's administration will support any IRCop's decision to use /kill if the situation appears to have warranted it. It is always helpful to have logs provided by two operators.
  2. Link servers back after a net split with direct or remote commands. This is the main duty of an IRCop.
  3. Be a peacemaker. Use the path of least resistance when administering discipline or solving problems. In other words, use common sense.

An IRCop does NOT have the right to:

  1. Use their power in personal disagreements. The moment a confrontation becomes personal, the IRCop effectively loses their status. Should it be deemed that an IRCop misused their power, their status will be reviewed by Deepspace's Administration.
  2. Allow others to use their O-line, either directly or indirectly. Doing so will result in the immediate removal of the oper block.
  3. Carry user modes that make them appear to be persons they are not. (An example of this is +A - Server Administrator.).

IRCop Duties:

If an IRCop logs online and they notice that there are no other IRCops online then they should oper up if they have time. If they are not up to par on a certain day, then please do not oper up and explain to your Server Administrator your situation.

IRCops are required to spend a portion of their time online opered up and in ONE or more of the following channels:

  1. #Services
  2. #Beginner
  3. #NetInfo
  4. #NOC
  5. Any other help channel that they so desire.

Local Operators:

Local operators are the staff, or representatives, of a single server. That Server Administrator is solely responsible for its local operator's actions and training. A local operator only has access to that server, and that server alone. No backup oper blocks are given a local operator. This is a good time for the local operator to study diligently on commands and workings of the network, in the event, they are promoted to global operator in the future.

Channel Founders:

Channel founders have the sole ownership and discretion of their channels. It is totally up to them what rules they wish to enforce and who they select as chanops and allow access. They are also responsible for any decisions about discipline (kicks, bans, akicks) in their respective channels. Be wise with your decisions. Network Administrators deal with network matters, not channel matters. Channel founders will also be encouraged to host web page for their channel(s) on Deepspace. The Deepspace staff will assist the founder or the founder's designated channel operator in the development of the web page, review the page, and post it to the proper Deepspace host server.


The technical or managerial functions that serve to implement the overall network policies decided by the Network Administrators.

The principal services provided by Deepspace: (Please do not confuse this with Web Services as listed on the "HOME" or index page.)

  1. NickServ Services: User-based control functions for nickname recording.
  2. ChanServ Services: Channel-based control functions to channel operators.
  3. MemoServ Services: Support features and functions messaging services.
  4. OperServ Services: Global network control functions and operator server.
  5. HOST Services: Systems that run the programs used by or for Deepspace.

If you need help with any of the services commands available to normal users type: /msg nickserv help, /msg chanserv help, or /msg memoserv help.

If after viewing the helpfiles you still need assistance with services please join #Services channel.

A list of the commands and a thorough discussion on their use(s) is also included as a separate section of this handbook.

Users needing online help with questions involving IRC commands are asked to join #Beginner channel.

If help is unavailable in the proper channel, please stay in that channel and issue a /helpop message describing your problem and the channel you are in. For example: /helpop Having trouble with NickServ, I'm in #Services, no one in the channel except me.

Deepspace General Provisions:


In order to maintain a reasonable amount of similarity throughout the network, a Deepspace server must conform to the following basic requirements:

  1. Port 7050 will be set as the default port set in the link blocks and will be used for server to server connections.
  2. Port 6667 and 7000 must be open to the general public.
  3. Each server must make available the rules found at and in their ircd directory as ircd.rules.
  4. Each server must have the link blocks for all servers connected to Deepspace in their links.conf file.
  5. For the sake of uniformity and better management, server's Unreal3.2 directory needs to contain the following:
    • unrealircd.conf
    • opers.conf
    • links.conf
    • ircd.motd (see requirements below)
    • oper.motd
  6. Each server's ircd.motd file must contain, at a minimum, the following details:
    • Administrator's nick and email address.
    • Co-Administrator's nick and email address. (if applicable)
    • Nicks of the server's IRCops and local opers.
    • Ports open on the server.
    • Physical location.
    • URL to Deepspace's Webpage:
    • URL to Deepspace's Forum:

New Server Links:

To link a server an application needs to be presented to the Network Administrators with pertinent information (i.e. uptime, speed, physical location, server owner name, your own name and e-mail address, and anything else you deem important) so it can be reviewed for a vote.

The Network Administrators will address all new server applications. After reviewing the application, an e-mail vote will be administered. The Network Administrators, by majority vote, will decide whether to permanently add a server to the network.

If after the majority decides to add the server, there will be a 30 day probationary period to make sure both parties are satisfied with the link and that the high standards of Deepspace are met. During this probationary period, the server will not be allowed to add any global oper blocks and the server will be reviewed and watched by the current Network Administrators. Also during this period, the new server will only be allowed one link block in another server of the Network Administrator's choosing. At the end of the probationary period, the Network Administrators will decide whether or not to extend full privileges to the applicant server. If all is well, the new server will be granted permanent linking privileges and link blocks added in the remaining Deepspace servers.

Prohibited Activities:

(Prohibitied activities)

  1. No Trading of Porn or Warez or Channels with that content.
  2. No Sexually Oriented Channels, or Channel Names
  3. No Offensive or Vulgar Channels or Channel Names.
  4. No Offensive Nicks in #Lobby.
  5. No Nuking in any way, shape or form.
  6. No Flooding services or users.
  7. No bots allowed of any sort without permission from NetAdmin.
  8. No Attempted Takeovers.
  9. No begging for ircOP status. It is earned and a privilege.
  10. No use of proxys are allowed on this server. Any abuse of this and/or flooding server with connections and appropriate actions will be taken.
  11. Please refrain from using profanity in the family channels. We have children that visit us in #Lobby.

We reserve the right to deny access to this server and this network to any user, host, or site without warning or explanation.

Anyone found not following the rules of this server, or the rules of Deepspace IRC Network will be banned.

By using this server, you consent to all of the server rules, and the rules of DeepSpace IRC Network.


  1. Violators will be advised and warned, and then if repeated will be removed without warning or appeal.
  2. Temporary bans may be placed on an individual if the offense is not considered too extreme. Temporary bans last for three days or seventy-two (72) hours. If a temporary ban is evaded then the ban will become permanent.
  3. Logs will be kept of the prohibited activities and used in the process of decision making of the administration for further actions.

If you have tried everything and are still unable to connect then please read the following: Unable to Connect. After reading this file, you may send an e-mail to the Network Administration to explain why you should be exempted from the ban. We value your visits, your input, your friendship and for being a part of Deepspace. We will do all in our power to keep your visits to Deepspace safe and secure.

Thank You,

Deepspace Network Founders/Administrators: CHTANK, Johnc, Linz, Login, PwcrLinux, sahara
Deepspace Technical Administrator: Xgizzmo, Icemech

Download the Deepspace Declaration

If you have any questions or comments, please address them to the Network Administration
Webmaster: DeepSpace Webmaster - © - All rights reserved.