[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: +b/+e chains
- To: ircd-users@xxxxxxx
- Subject: Re: +b/+e chains
- From: Christophe Kalt <kalt@xxxxxxxxxxx>
- Date: Thu, 17 Dec 1998 08:34:28 -0500
- Delivered-to: ircd-users-out@irc.org
- Delivered-to: ircd-users@irc.org
- In-reply-to: <199812170659.JAA05494@hub.kbsu.ru>; from Eugene L. Vorokov on Thu, Dec 17, 1998 at 09:59:54AM +0300
- Mail-followup-to: ircd-users@irc.org
- References: <199812170659.JAA05494@hub.kbsu.ru>
[redirecting to ircd-users, the original message is quoted
in its entirety]
On Dec 17, Eugene L. Vorokov wrote:
| Now, when you have a ban on channel and an exception matching
| that ban, you cannot set another ban that matches both previous
| ban and exception. I think this is a good idea to have such
| +b/+e chains. A little example:
|
| We have +b *!*@*.com. Then we want to set exception for
| *.anet.com, and we add +e *!*@*.anet.com. But then we also want
| irc.anet.com to be banned anyway. When we try to set +b *!*@irc.anet.com,
| we won't be able to do it due to existing ban *!*@*.com. I think
| it should be allowed, since this new ban matches an exception and
| is "more exact" than exception. Then, if we want shekel@xxxxxxxxxxxx
| not to be banned, we also can set +e *!shekel@xxxxxxxxxxxx, and
| etc. I think you got an idea: new +b or +e should be settable in
| such cases to organize +b/+e chains, where more exact +b or +e
| should have higher priority.
even if adding the !*@irc.anet.com ban was possible, it
would not change anything: irc.anet.com matches *.anet.com
THUS is it NOT banned.
+e are EXCEPTIONS to bans, +b are NOT exceptions to +e.