♫ This was a headache… ♫
I have never appreciated the W3C as much as I do now. Much as we all may hate their unreadable specifications, at least they enforce a certain amount of standardization, and they ensure that there is decent documentation available. I sincerely wish the the W3C would decide that IRC is in its bailiwick, and enforce certain standards.
We (Eric and I) decided that it would be kinda nice to have an IRC server, we obtained permission, and we looked around for a good one to install. I discover an irc server that appears to be simply known as ‘ircd’. I figure that that must be the official irc server, since otherwise it would be known as ‘johnny’s ircd’, or something of the sort. So Eric installs it.
Now I need to set it up so that my bot and I can become operators. I look around, find the documentation for an irc server known simply as ‘ircd’, and discover that I just have to add a password-file-like line to /etc/ircd/ircd.conf. I add the line, although it looks rather out-of-place. Now, the IRC server won’t start up anymore.
So I remove the line, and keep looking around. After about an hour, I discover that I’m running the undernet irc server. These other sites are have the documentation for a different ‘ircd’ (for which I could not find a name). So I turn back to my local installation, find the docs, and find the example.conf file. Ultimately, I discover that the code to make myself an operator is:
Operator {
host = "*@*.*";
password = "$PLAIN$mypassword";
name = "bytbox";
class = "Opers";
mode_lchan=yes;
};
Eric restarts the server, and I discover that it works.
Now, I want to use my server operator privileges to make myself a channel operator. This I never found out how to do – I could not find the relevant documentation, there were no good man pages, and the ‘OPMODE’ command was ‘disabled’. I tried 4 different methods of enabling it, and none of them worked. And, of course, whenever there was documentation online, it claimed to be the ‘ircd’ documentation. Thanks, google.
Related posts:
