csircd not compliant

[tabarnac]

From irc.nac.net:

NETWORK=EFnet STD=i-d STATUSMSG=@+ PREFIX=(ov)@+ CHANTYPES=#& NICKLEN=9 TOPICLEN=120 KICKLEN=120 CHANMODES=b,k,l,imnpst
MODES=4 MAXBANS=40 CASEMAPPING=rfc1459 CHARSET=ascii MAXCHANNELS=20 are supported by this server

Nice to see a RAW005 (compared to prison.net), but the maxbans is now 100 and modes +e/+I are not supported by this server.

If nac's hub is about to be hubbing leafs, a desync party will begin!

[Hwy]

nac's hub is not csircd, it's a modified Hybrid 6:

20h 12 :: *** 2.8/hybrid-6.3.1(20020418_1). ircd.nac.net ACGHiKMpZ TS5owc
20h 12 :: *** SUPPORTLAMERS=0 GOAWAYBITCH=all are supported by this server

The 005 is a joke message, so looking into the VERSION flags:

It doesn't support setting +e locally (no 'e' in the VERSION flags), but because of a patch leeh did, it WILL propagate them properly. It does not support +I at all.

From /stats ? entries:

irc.nac.net[unknown@255.255.255.255] 487 649070793 48369662 32730917 2311234 5941720 0 TS QS CHW
ircd.nac.net<->irc.nac.net, no +e, no +I, no ENCAP (for OperSpy)

ircd.nac.net[unknown@255.255.255.255] 0 96477183 7049217 4792226 359842 830691 0 TS QS EX CHW KNOCK
ircd.nac.net<->ircd.servercentral.net (and the rest of the world), yes +e, no +I, no ENCAP

For the MAXBANS issue, all servers can exceed MAXBANS and not desync them. MAXBANS just limits how many +beI a client can set. Thanks to a developer for this verification.

This, of course, is not the place to complain. In addition, if you wish to complain, please have all the information you need FIRST.

PS. 005 RPL_ISUPPORT was introduced in csircd 1.14.

[leeh]

It doesn't support setting +e locally (no 'e' in the VERSION flags), but because of a patch leeh did, it WILL propagate them properly. It does not support +I at all.

Actually, I think when I did it in 6.3.1 I missed something lower down and it was still broken for propagation..

[tabarnac]

Nice to see a RAW005 (compared to prison.net), but the maxbans is now 100 and modes +e/+I are not supported by this server.

When a bot is supporting +e modes and it's owner is too lame to figure out that the bot ended up on the lame irc.nac.net server, it has the nice result of locking up a channel or something like that.

by doing /mode #channel +e nick!ident@host
the server will set channel mode +int

Instead of leaving the IRCd setting unwanted modes, why just not give an error message, like "+I This mode is not recognized by this server" or something similar when a mode isn't supported? And why is +e/+I still not supported yet on csircd? lazy? If you can't follow, get out.

Time to kick a lazy butt.

[munky]

i believe it does give an error, but i think the SOP is to give an error for the unknown modes, and continue parsing the known modes.

[leeh]

When a bot is supporting +e modes and it's owner is too lame to figure out that the bot ended up on the lame irc.nac.net server, it has the nice result of locking up a channel or something like that.

Instead of leaving the IRCd setting unwanted modes, why just not give an error message, like "+I This mode is not recognized by this server" or something similar when a mode isn't supported? And why is +e/+I still not supported yet on csircd? lazy? If you can't follow, get out.

No client should use +eI modes, unless its advertised in 005 - its standard enough nowadays for that to be done. Clients are also used to servers ignoring unknown modes, you cant just change something like that randomly because you feel like it, because it may break more than it will fix.

As for csircd, +eI does exist there, just not in a release version -- prison is running a csircd beta with it in.