[IRCServices] .29 mlock issue

[Andrew Church]

     Given the complexity of Unreal's +f mode, I don't really see checking
this programatically as feasible; the simple answer is "don't do that".  If
it causes too many problems, I'll just remove MLOCK +f support entirely.

  --Andrew Church
    achurch at achurch.org
    http://achurch.org/

>
>hi,
>
>chanserv allows you to mlock -modes that gets +'d with channel mode +f.
>
>/msg chanserv set #channel mlock +ntSNT-miC+f
>[7c#C5,10j#i10,10k#K10,5m#m2]:10
>
>for example, it allows you to add -m and +m (inside +f) rendering the mode
>useless.
>
>-- example --
>[11:32] <asdsd> 1 sadfasdfasdfasdf
>[11:32] <asdsd> 2 dsfsdfgsdfgsdfgsdf
>[11:32] <asdsd> 3 ghndghndghngdhngfhngf
>[11:32] <asdsd> 4 dfghnjhfgjhfkjhjkgh
>[11:32] <asdsd> 5 dfgsdfgsdfgdsfgsdfg
>[11:32] <asdsd> 6 dfgdsafgsdfgfsghfdgh
>[11:32] [mode:#shadowfire] (TriGun.ShadowFire.ORG!) +m
>[11:32] [mode:#shadowfire] (ChanServ!services at shadowfire.org) -m
>[11:32] <asdsd> 11 fhdghjfhljgjkglki./hkl
>-- /example --
>
>will it be possible to add more strict checking when adding mlocks with
>+f?
>
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices