ClueNet is looking for a new Chief Technical Admin. More information here.

Shellsnet:SN ServersAndStaff

From ClueWiki

Jump to: navigation, search

Important Note: This is a backed up copy of what existed on Shellsnet's old wiki.

This article is a part of the ShellsNet Old Wiki Backup index

Do not modify this page!




Contents

[edit] Shellsnet.org IRCD List

Server Location Admin Operator(s)Hosted by
irc.shellsnet.org - - - -
mlg3.us.shellsnet.org USA, CA <censored> Narf mlg3.net
theforest.us.shellsnet.org USA, FL Wolf - daforest.org
rulex.eu.shellsnet.org EU, Finland Gigapikseli Tazikas rulex.net
anarxist.eu.shellsnet.org EU, NL Favorit - anarxi.st

Please note that :

  • Normal IRC connections use port 6667. SSL can be used on port 9999.
  • All servers are protected by the SN ISS.
  • Identd may be required to connect to some servers, or to connect to SN at all from ISPs/countries. You should read the [helpful guide to enabling identd].

[edit] IRCD/Server Linking

[edit] Read this before asking to link a server

Note that ShellsNet.org only allows new ircds to be linked to its network very rarely, in cases where the server is actually needed. We do not grant IRCD links to people who come on IRC and just ask us, neither do we grant IRCD links to every admin who affiliates with us. In fact, the vast majority of admins affiliated with ShellsNet DO NOT have an IRCD linked to ShellsNet, nor do they have IRCops. Only a few shell provider admins become ircops, and even fewer are granted permission to link an IRCD. The reasons for this are simple :

  • We only need about 3 ircds linked into our network, with maybe one or two more for redundancy. Anything beyond that is a waste of time and effort, and would make managing the network much more complicated than it needs to be.
  • Most people who ask to link an IRCD to us don't have a server we'd consider good enough, nor do they have the skills, experience or wisdom we require of our server admins. We get so many requests from people to link IRCDs into our network that is simply too time consuming to testlink them all to find the few ones which are good... instead, when we need a new ircd linked then we ask our existing, trusted admins to supply one.

If you want to "be part of ShellsNet", then the best thing you as an admin can do is get affiliated and start USING ShellsNet for chatting with other admins and users, so we can both learn about and from each other. That is a much better way to join us then trying link an IRCD.

That said, if you really do want to link an IRCD, the requirements are listed below.

[edit] IRCD Linking Requirements

  • The new ircd must actually be needed.
  • The new ircd must be of excellent quality. In particular, it must have excellent stability.
  • The server the ircd would run on must be capable of running our software (a modified version of bahamut1.8).
  • The Linking Admin must either be competent enough as an IRCD admin to setup up and maintain the IRCD themselves and have the experience to prove this (as judged by <censored> and Wolf, admins with many years of experience in running IRC networks), OR they must be willing to let another staff member (appointed by <censored>) log in to the ircd shell account and manage the ircd for them.
  • The Linking Admin must be demonstrably trustworthy, as judged by <censored>. This typically means they must have been affiliated with SN for at least a year, and have done things which clearly demonstrate their good judgement, loyalty and general trustworthyness, such as work constructively with the other affiliate admins on several projects.

Note that <censored> reserves the right to delink existing IRCDs from ShellsNet if any of the conditions above cease to be met during the time the IRCD is linked. In cases where an IRCD is delinked, unless it is an emergency, reasonable effort will be made to contact the admin of that IRCD in advance and explain why.

Personal tools
Server information
Useless