Dear List Server Network,
I have recently started to look into allocating bandwidth into starting my own list server network and I was flatly refused when I asked for the list server program itself.
After doing a bit of thinking, I have concluded that you are just trying to conserve the nature of JJ2 by only having one network where people fall under the supreign rule of people who are supposed to be gods. This is not the case for other networks, however.
If we put this North American list servers that are networked to the big uber super list server of DEATH against the number of IRC servers in the EFNet network, we will get some big results:
The A represents Mono's server, the house represents my house.
Now, imagine that the list servers are an IRC network that's newly started. Suppose you start to get flooded with requests to link to a new server, supposedly to spread the word in that particular area. You can either allow them to do so, or flatly refuse them.
Judging by the look on your face, of COURSE you'll say no. This is because of the following reasons:
- You are overly concerned about the safety of your network, which is a bit too careful
- You think that the bandwidth is distributed evenly enough
- You might be xenophobes
Well, maybe some people want your code for the server you're using, probably to start their own network or help fix up exploits. And you'll still flatly refuse them, backed by the list of stuff above. This is exactly the case with the current list server network you are running.
Now, let's compare developmental standards. Nebula is working on a new list program (closed), whereas Whats-His-Face is working on an IRCd (open). Suppose both of our friends find an exploit in their software. Since Nebula's list server's a closed-source program, he or a friend of his will need to work for hours or even days to close the loophole. However, since Whats-His-Face has his code open-source, a large group of programmers gather in a chat room somewhere and end up fixing the program in a few hours. So, at the end of the day, WHF has fixed his loophole faster with the help of contributors, whereas our friend Nebula could still be working on it.
Lastly, users and administrators. I will be using #jj2 for the IRC example. Suppose a hazardous user comes into the channel/list server and starts to do some activity (eg, spam, hacking, etc). Both the ops and admins will boot the user, but this is not always the case. #jj2's operators will often boot people on a whim. In this case, you are better.
Overall, my comparison proves that the system presented by a typical IRC server is more friendly than the system that you have presented. I'm sorry to say this, but the truth hurts.
Thankfully not yours,
Peter S. Conway