Anope IRC Services

Anope Development => Feature Requests => Topic started by: Raffaele Nntifrega on February 12, 2009, 04:58:36 PM

Title: [ChanServ] Clear command (stop flood)
Post by: Raffaele Nntifrega on February 12, 2009, 04:58:36 PM

Hi, i think anope needs a feature to stop flooding while clearing the channel.
Do more events on one line.
Example:
Instead of:

[25:61:13] * Bot sets mode: -b test!*@*
[25:61:14] * Bot sets mode: -b testt!*@*
[25:61:14] * Bot sets mode: -b testtt!*@*
[25:61:14] * Bot sets mode: -b testttt!*@*
[25:61:14] * Bot sets mode: -b testtttt!*@*
[25:61:14] * Bot sets mode: -b testttttt!*@*
[25:61:14] * Bot sets mode: -b testtttttt!*@*
[25:61:14] * Bot sets mode: -b testttttttt!*@*
[25:61:14] * Bot sets mode: -b testtttttttt!*@*
[25:61:14] * Bot sets mode: -b testttttttttt!*@*

Would be better:

 * Bot sets mode -bbbbbbbbbb test!*@* testt!*@* testtt!*@* testttt!*@* testtttt!*@* testttttt!*@* testtttttt!*@* testttttttt!*@* testtttttttt!*@* testttttttttt!*@*
Edited: ... errata corrige :P

Title: Re: [ChanServ] Clear command (stop flood)
Post by: katsklaw on February 12, 2009, 06:05:56 PM

Problem is this will rely on each individual IRCd since each one allows a different number of stacked modes. For example ircd1 only allows 3 stacked modes, ircd2 will allow 6 but only if they are the same type and only 4 modes of mixed types and so on. So that said changes to the conf parser, the ircd proto stuct and a revision to do_mode to say the least is called for. Which could result in a few hours of code changes at minimum.

A faster solution is if you have a lot of modes to change, do it yourself in your own client, not with services. Additionally, this isn't a flood of any kind. Yes, it's lines of mode changes, but that doesn't make it a flood.

PS: it's Anope, not Adobe.

Title: Re: [ChanServ] Clear command (stop flood)
Post by: Robin Burchell on February 12, 2009, 07:06:51 PM

This is planned eventually, but is not high priority.

Thanks!

Title: Re: [ChanServ] Clear command (stop flood)
Post by: Raffaele Nntifrega on February 12, 2009, 10:24:20 PM

Quote from: katsklaw on February 12, 2009, 06:05:56 PM

Problem is this will rely on each individual IRCd since each one allows a different number of stacked modes. For example ircd1 only allows 3 stacked modes, ircd2 will allow 6 but only if they are the same type and only 4 modes of mixed types and so on. So that said changes to the conf parser, the ircd proto stuct and a revision to do_mode to say the least is called for. Which could result in a few hours of code changes at minimum.

A faster solution is if you have a lot of modes to change, do it yourself in your own client, not with services. Additionally, this isn't a flood of any kind. Yes, it's lines of mode changes, but that doesn't make it a flood.

PS: it's Anope, not Adobe.

Here is the raw sent on join from the IRCD:
TOPICLEN=308 KICKLEN=256 MAXTARGETS=20 AWAYLEN=201 CHANMODES=Ibeg,k,FJLfjl,ABCDGKMNOPQRSTcimnprstz FNC NETWORK=Anope MAXPARA=32 ELIST=MU EXTBAN=,SsMRmOTpNQrjcBA EXCEPTS=e CALLERID=g INVEX=I are supported by this server

as u can see MAXTARGET or MAXPARA should be the value, this message is an IRC standard (i mean that have to stay there :P).

Quote

This is planned eventually, but is not high priority.

Thanks!

np  ;D

P.S. i edited the first post with "anope"  ty

Title: Re: [ChanServ] Clear command (stop flood)
Post by: Josh Johnson on February 13, 2009, 12:21:53 AM

I don't think servers get that sort raw on connect/netburst... I don't know. I'll check that and post back.

Update: Apparently InspIRCd sends a command that's called `CAPAB` which has some of the capabilities of the server. (I completely forgot about this. :P) I suppose it's completely possible with most/all IRCds with some protocol module edits; that is, if the Anope devs are up to it. :)

Title: Re: [ChanServ] Clear command (stop flood)
Post by: deiks on February 13, 2009, 07:05:43 AM

Well how about in some way:

if protocol is unreal use 12
else protocol is inspircd use 10
.
.
.

:)