The SorceryNet website would like to use cookies to improve your experience on our website. This notice is in accordance with the EU Cookie Directive, some cookies essential for the operation of this site may have already been set, please configure your browser to block / delete them if you feel it necessary for your privacy.

EU Cookie Directive Module Information
Linking Information SorceryNet IRC Chat Network - irc.sorcery.net http://www.sorcery.net/index.php?option=com_content&view=category&id=93&layout=blog&Itemid=62 Sun, 22 Oct 2017 09:52:04 +0000 Joomla! 1.5 - Open Source Content Management en-gb Linking information http://www.sorcery.net/index.php?option=com_content&view=article&id=49:linking-information&catid=93:linking-information&Itemid=62 http://www.sorcery.net/index.php?option=com_content&view=article&id=49:linking-information&catid=93:linking-information&Itemid=62 If you're interested in linking a server to SorceryNet, one of the first things you should do is read our charter. The charter defines the administrative procedures and we expect prospective administrators to be familiar with it. It also provides a documented overview of the application process, voting process and server requirements.

This document can supplement to any requirements that are in the charter. It can not remove requirements listed there, but it can extend them.

The next, but maybe even more important, step is to get to know your future colleagues. As you've read in the charter, every administrator on this network has an equal vote in network decisions, so we're not very likely to accept a complete stranger. Take some time to hang around in #help & #sorcery, speak with staff, help users and make yourself familiar with the way this network is run. You might also visit other official channels which you can find listed in various server MOTDs.

It's strongly suggested to be subscribed to the sorcery@sorcery.net mailing list for a few months before applying. This will give you a bit more background into our network and keep you apprised of other server applications, and whether or not they were accepted.

Of course, there's the technical part of the application. Your server should be available 24/7, with a stable connection and enough bandwidth available to IRCd. You should also make sure that our IRCd runs properly on the operating system of your choice. We run our own IRCd called SorIRCd. You can get this source from the Applications team in #Applications or by sending them an e-mail.

Once this is complete, doublecheck the requirements listed below and fill in the form at the bottom of this page. Then send the application to our coordinator at applications@sorcery.net. After making sure all requirements are met the applications team will start the linking process by sending a call for discussion (CFD) to the sorcery@ mailinglist. You will be contacted by our staff to testlink the server, and some tests will be performed to estimate its performance and stability during this period. The process will be concluded by a call for votes (CFV). During this period all current administrators will cast their vote, and the results will be announced on the mailinglist. When a majority votes in favour of your server, your testlink will be converted to a permanent one.

More detail regarding the entire process can be found in the charter, section 5.1.

Requirements


Now, for a little more formal list of requirements:

 

General Server Requirements:

  1. Your server must be available for the long term.
  2. Your nickname must have been registered for at least 2 months.
  3. You must have ports 6667, 6697 (ssl), 7000, 9000, and 9999 (ssl) open to the world for client connections and 9099 (ssl) for server connections.
  4. You must be able to accept SSL connections for SSL encrypted traffic.
  5. Client servers must be capable of supporting at least 1000 concurrent clients.
  6. You must be able to compile our ircd server software (SorIRCd) on your server. This requires POSIX compliance. Linux with a 2.6 kernel is strongly recommended.
  7. You must have a stable time base, either through ntpd or an other solution.
  8. You should not have other high bandwidth tasks running on the machine, such as an IRC daemon on a competing network, or a high traffic ftp or rsync mirror).


Technical Server Requirements:

  1. At least 256MB RAM for a dedicated machine. In the case that this is a virtual machine, the guest must have access to at least 256MB of ram. More will be required in the case that the machine handles other tasks.
  2. At least 3mbit of internet bandwidth, preferably with multiple uplinks or a Tier 1 backbone uplink.
  3. If you are using virtualization software, we require proof of a stable timebase. Xen with a stable time config is recommended.
  4. You should be able to run at least 50 background processes.


Overall Recommendations:
(While not strictly requirements, these are strongly recommended to make things easier for both you and us).

  1. A modern processor is strongly recommended for ease of replacing parts in case of failure.
  2. You should be comfortable compiling and configuring software on your machine with minimal assistance. In most cases, other admins and most opers will be able to assist you, but the final responsibility to make things go is yours.
  3. You should be familiar with our policies and some of our staff, server admins are preferable.
  4. You should understand how to update your machine to patch exploits, or make sure the root user does. As an IRC server, your machine will be somewhat high-profile and a target for attempted exploits.
  5. If you do need administrative assistance with your machine, it is recommended that you run the newest release of either Debian or Gentoo linux. We have a fairly strong #linux channel, where those distributions are the most common so the easiest to get support for.

Please do not proceed with this application until you have fulfilled these requirements. Failure to do so will lead to your application being rejected.

continue with the application form...

]]>
jc@sorcery.net (SorceryNet) Linking Information Tue, 24 Mar 2009 19:00:00 +0000