Asmo
Site Admin
Joined: 26 Oct 2004
Posts: 675
Location: Undernet
|
 Posted: Sat Oct 01, 2005 10:24 am?? ?Post subject: IRCu 2.10.12 Released (updated)
|
 |
|
Undernet's IRCd ircu2.10.12 has been released yesterday.
Among the changes are:
- The configuration file is now based on the configuration parser found in ircd-hybrid, which makes it far easier to read and edit. Here is an example of how an IRC Operator is added, the previous "O:Line":
Operator {
local = no;
host = "*@*.isp.com";
password = "VRKLKuGKn0jLt";
name = "Nick";
class = "Local";
};
- Full IPv6 support.
- Support to check new connections with an IAUTH external authorization server. From the Changelog: "This allows an external program to accept or reject any client that connects to the server and allows that external program to assign an account stamp to the incoming user."
- New channelmodes called Oplevels. "It uses new channel keys (+A for the administrator, +U for users) to grant chanop status when you join using those keys. Part of this channel protection is that you cannot be deopped in channel by someone who you opped."
- New channel mode +D which can be used for channels where the majority of users only are listening. Only users who are opped, voiced or send a message (when the channel is not +m) will sent a JOIN out to the other users. This is handy for example in class channels.
- Commands that send messages to services can be added in the configuration file. This way you can make /X send commands to X, etc.
- The /stats command now accepts more descriptive strongs then single letters. So /stats access shows the same information as /stats i. Typing /stats will show all possible strings.
- You can use CIDR notations in the configuration file rather then wildcards alone.
- And lots more, a 320kb changelog comes with the download.
You can find the download here.
Edit: The Undernet Help project has updated their site with more information on the new channel modes. So if you like a better description on how to use these new modes, you can find the information here.
Edit 2: I forgot all about one feature I like to see long time ago in IRCu: /silence excemptions. Using /silence +~*host@to.excempt you will be able to still receive messages from that host even if you added *@* on your silence list. Silence is a better way to ignore users then /ignore, as the last is client side which still results in you being disconnected on large floods for example. Silence is a server side command so the text is simply not being sent to the client at all.
_________________
Asmo
webmaster www.IRC-Junkie.org
|
|
???
