On Fri, Dec 18, 2009 at 11:05 AM, PapaSmurf <freedried@yahoo.com> wrote:
2.2.2 Founders (ChanServ ACC 5/4/3) can be akick'd, but AOps/SOps cannot. ChanServ ACC 3 founders can ADD/DEL SOps. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It sounds like a bug. if AOP/SOP have that protection, founder should too.
2.2.3 AOps/SOps cannot be added if their nick/address is on the akick list. 2.2.4 Akicks (ChanServ ACC -1) can be bypassed if the akick'd matches founder/SOp/AOp ^^^^^^^^^^^^
It would seem that 2.2.3 is counterproductive and probably unwanted then. If AKICKs can be bypassed due to an AOP or SOP match, it is conceivable, the Founder might want to add someone as AOP in order to allow them to bypass akick. An example would be: AKick *!*@*.aol.com but give a 'friend from AOL' AOP access. In addition to setting a channel mode +e except. Actually an '/ChanServ AKEXCEPT' or '/ChanServ EXCEPT' list would be more proper here.
2.2.5 Founders can be akick'd by anyone with an access of ChanServ ACC -1 or higher (5/4/3/2/1/0/-1) as long as they match any SOp or higher's (ACC 5/4/3/2) access list. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I'm not sure what was meant here.. I don't think someone with ACC -1 can set any akicks. Assuming the channel has IDENT enabled, I believe identification to a SOP or higher nickname is required, and ChanServ ACC 2 or higher is required...
ANSWER: The founder changes founder name, but still uses the original founder name (to visit the channel).
In that case, (of course), the original name is no longer Founder. ChanServ doesn't currently allow multiple founders. ---------
4.2.1 ChanServ mkick and channel excepts.
Excepts (channel mode +e) are designed to allow people in who match a large ban set (from abusive users, etc). If a guest is on the except list and an mkick is issued (by the highest ranking op on the channel), guess who ChanServ doesn't kick? Right, the guest. Mass kick does not unset excepts, and allows excepts to remain in the channel throughout the mass kick process.
I would suggest that this a bug, as it defeats the purpose of the MKICK command, as we originally recommended it, as it was proposed, that is, and as it got implemented... And it stands as a significant reduction in MKICK's usefulness. MKICK is meant to completely purge a channel, as the "sledgehammer" against takeover and desync situations. Purging even +e users is imperative for MKICK to really be useful in the most extreme circumstances, as +e users are still members of the channel... Obviously the channel won't be emptied and reset, if some people are left in the channel after a MKICK. And most importantly, special channel modes such as "+k" could be left in place, leaving the SOPs and FOUNDER locked out of their channel. --------- -- -J