Well first off if a person gets 100 access on a channel and abuses
it. Its the 400+ person's fault for adding the person with that access in
the first place. Second off. a 101+ can easily remove the ban suspend the
user and thus a solution to the problem. As for the "unban" being the same
issue. So far from what I've seen if a ban is placed that matches another
ban in X. The other bans will automaticly be removed/overwritten within X
unless placed at a higher level than the user issuing the current ban has.
And yet again if such things are abused that is basicly the fault of the
higher leveled user. As for the problem of it being globally abused. If
chans are caught doing that they should just have X revoked from the
channel. Disallowing the *!*@* ban would just be putting a restriction that
shouldn't be in place if that is intend what you had in mind for a solution.
Ultimately from what I last remembered UnderNet's policy on such things is
user controled. If it happens in a channel. It should be handled by the
channel ops (superior if required). If abuse continues to take place. Then
CSC gets involved whereas the particular administrator can use his/her
descretion as how to "deal" with the issue.
Brian "TGS" Gilliford
----- Original Message -----
From: "Alexander Maassen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, April 29, 2002 1:45 PM
Subject: [Coder-Com] *!*@* ban abusability
> Problem:
> *!*@* masks strongly mess up channels when used in kick/ban
>
> Example:
> - Get level 100 in a channel (so you can ban)
> - Issue a ban on *!*@* at level 20
>
> Result:
> Flood away, coz noone can op himself since he is no longer allowed to be
op
> (*!*@* matches all users and equals NOOP that way with the difference that
> every 100+ can do that without needing permission from a 450+)
>
> Solution:
> Finally get rid of *!*@* usage !, its only abused by a lot of users (Greg,
> perhaps you want to start logging the *!*@* usage to get some stats
> yourself) to create massjoinfloods, disrupt the channel activity and in
that
> way be able to put load on the servers. *!*@* bans are NOT NEEDED TO BE
USED
> by clients, perhaps in kick if they want to clean up the idlers, but then
I
> suggest to limit the usage of kicks on *!*@* to 450, perhaps split the
> command apart and make a /msg X kickall <channel> <reason> instead
>
> Another funny issue you haven't thought about is the fact that unban is
also
> affected by this issue, imagine having like 20 bans on a channel's banlist
> in X, someone adding a ban on *!*@*, now do the math and make an
estimation
> what you need to do to remove this single ban without harming the other
bans
> in the list.
>
>
