On Fri, Jan 1, 2010 at 12:00 PM, PapaSmurf <freedried@yahoo.com> wrote:
I believe it was James Hess , on this mailing list, who stated he was unsure what I meant by section 2.2.5.... Someone is akick'd. The akick'd is on a SOp's (or the founder's) access list. That akick'd user can akick the founder, under current services, if the founder is not concurrently added to the SOp list (as well as being named founder). As far as I know, if the founder is identified to their nickname, or to ChanServ, then ChanServ will not enforce an akick against them, and they will always be able to use the /CS UNBAN command, so they can't be "akicked" in any case..
It is possible to akick *!*@*.*, even though some SOps' last address would clearly be matched by the pattern (unless the SOp list is empty). So is there now something that prevents a mask that matches a current online SOp's host from being added to the list? As far as I know it is (or used to be possible) to SOp *!*@*.*, and still akick *!*@* although this is not recommended for obvious reasons. Apparently adding an akick by nickname doesn't work for a SOP. It's probably more a side-effect of the nickname already existing in the list though (with different flags). Observe, you can't add an AOP listed by nickname to the akick listed by nickname either. In general, using MASKs instead of NICKNAMEs in OP lists is deprecated, or SHOULD have been deprecated a long time ago. New channels can only be registered to NickServ nicknames now... It's not possible to forego NickServ registration and register your channel to a MASK or Set Founder to an address mask anymore. SOp list (and perhaps AOp list) should join the party, and new entries by NickServ nickname only. Except on "legacy" channels registered prior to some date, that have Ident disabled, and already use address masks to list some ops. -- -J