new ircd is not so far away

[Piotr KUCHARSKI <chopin@xxxxxxxxxx>]

Hello

Some of you know, some don't, but we're every day closer to
ircd 2.11.0. You can have a look at a very basic roadmap
here http://akson.sgh.waw.pl/~chopin/ircd/ROADMAP

We would like to hear your input on what you think
"a must" to be included in ircd (I know, UID is, but
consider it done).

Also, I'd like to ask you about some behaviour of ircd
we want to change. Some of them are: changing +r to
allow /nick (so far only when in form of uid from SAVE,
but perhaps even more -- instead disable stats etc.),
propagating +r; included RESTRICT_USERNAME, well, some
form of it -- it allows chars from (more-less) 32 to 
127, but there must be at least one alphanum and not
more than one nonalphanum (there's also restriction
about first char not being ~=+-); as 211 sends IP along
with UNICK, we will probably be able to do global clones
detection in, say, /24; also new command "ENCAP" will
give us basic framework for further extending ircd,
like introducing new commands, without need of waiting
through two ircd versions for new commands to work;
countless times we have been asked about different
log format -- now it's best time to do that; except
performance enhancements we will most likely include
some form of dealing with splits, no-op-on-split, not
accepting new clients when split (many of you use it
now in hemp patch); another feature will be mod_webproxy,
even turned on by default ;), also you will be able to
give 'reason' of rejection for each module; etc. etc.

I know, many of these are not real enhancements, some
are just toys (map command, lusers stats), but keep in
mind that this release will deal with one of the biggest,
imho, problems nowadays: nickname collisions. UID solution
is also known as Forced Nick Change (with some enhancements,
I must proudly add ;>), that is instead of removing both
users from irc, we will change their nicks. However, it is
not perfect in mixed environment. If collision occurs with
2.10 server, both nicks will be killed. Hence I will
encourage you all (next month or so) to do upgrades ASAP.

In the future we would like to kick out second biggest
problem: unfortunate (network troubles, DoSes) user
disconnections. More discussion will probably follow
in few months.

Ah, that's too much writing already. Now I'm waiting
for your input. There's still time for enhancements,
even for protocol changes. Speak up or be silent until
next version! :)

Happy new ircd^H^H^H^Hyear :)

p.