Those I gave the channel central to loved it because they just added the file to mIRC or their script and it worked without any other settings changes. That is what the users want. What they don't want is to have to stuff around making adjustments to anything that someone somewhere else gets loaded without any effort at all by the programme.
Thats exactly what I'm suggesting, note the part about "just loading a script." I say not only should it be configurable, it should be scriptable:
/chancentral -a +R You must use a registered nickname to enter
/chancentral -ap +f Flood control
/chancentral -r +R
(-a = add mode, -p = mode takes a param, -r = remove a mode). Then all someone needs to do is a simple ON LOAD script that executes the /chancentral commands and then the user has to do nothing else.
The big difference here is that mIRC's job is to support all RFC compatible IRCd's - a job it already does well and my channel central is there to support one particular network. In this case both mIRC and addons are doing their intended job.
Where does RFC1459 mention halfops? Ban exceptions? Invite lists? It doesn't. The latter two were originally added to mIRC and only functioned on IRCNet, if you used another network that had +eI it didn't work.
You are yet to convince me that discriminatory automation will benefit the users of mIRC as a whole and you probably never will.
Lets face it, mIRC discriminates. As you said, the server list consists of like 60% of the large nets, and the default selection is DALnet. mIRC discriminates in the channel folder by only including channels that Khaled/Tjerk choose, I really don't see how adding this to the equation signifigantly harms anyone. Your main reason against it is it is "unfair" well I reiterate, life is unfair. You are right, it is unfair, however it won't harm the people who use other networks, they can just simply add it themselves, and it will help those who do use those networks. So why is that such a big deal? I really don't see it.
