How new !channels work

Warning: this document is outdated


Goal

As we all know, #channels are subject to collisions which have very annoying side effects. Channel Delay is intended to prevent the collisions, but is far from being perfect.

These new channels will make collisions extremely unlikely.


How does it work?

In order to make collisions impossible, the channel name is assiocated to a unique ID. The pair (name , ID) will thus be unique as well.


The channel real name is built by concatenating the ID and the short name, for example, channel !foo might be !2B4dfoo. The ID has a constant length which makes it easy to separate it from the actual "friendly" name.


The channel creation must be requested. For example to create a the new channel foo, one must try to join !!foo.


In addition to a unique name, these channels obey to soe new simple rules:


New modes

As channel collisions are eliminated, it is possible to enhance the mode system.


general modes

+ r

reop mode, if the channel becomes opless for long enough, servers will re-op users in the channel. Note that not setting this mode can be used to create `modeless' channels (such as +channels) but with specific characteristics. (anonymous, secret...)

Reoping is done randomly by a random server. While it may sound like loading a channel with many clones increases greatly the chances of catching the reop, the randomization is done in a way which does not favor clones at all.


+a

This is anonymous mode, if toggled by the owner nobody can see who is talking or joining.

All you see is anonymous@blaha.com has joined

Example: 

06:46 ## Join !3B4OWchat: anonymous (anonymous@anonymous.)

You will see that when someone parts too.


user modes

+O

This mode is given to the creator of the channel by the server, it cannot be passed or gained after the channel was created. The creator is the only person able to set/unset r modes, and set (but not unset) +a.



Original text by: Christophe KaltOriginal URL: http://www.stealth.net/~kalt/irc/channel.htmlMaintained by: IRCnet.com TeamLast updated: 24.02.2002