[IRCServices Coding] ChanServ mode issue from other day

Russell Garrett rg at tcslon.com
Sun Sep 8 01:56:49 PDT 2002


Seems sensible, but I think IRCServices should stick to it's current
behaviour until +aoq are exclusive of each other i.e. until only one
can be set per user.

> -----Original Message-----
> From: ircservices-coding-admin at ircservices.za.net
> [mailto:ircservices-coding-admin at ircservices.za.net]On Behalf Of Aragon
> Gouveia
> Sent: 08 September 2002 00:35
> To: Ircservices-Coding (E-mail)
> Subject: [IRCServices Coding] ChanServ mode issue from other day
>
>
> Received this from codemastr...
>
> *** [Sat Sep  7 17:45:00 2002] MSG   : *codemastr* 3.1.4's is correct, we
> are still working on +q and +a in 3.2
> (~codemastr at rox-54B00D5.msns.str.ptd.net)
>
> If it weren't for the problem of clients I would say the ircd
> should work like this :
>
> - If you're a normal op, you get +o only.
> - If you're a protected op, you get +a only.
> - If you're a founder, you get +q only.
> - Each mode should work independant of each other.
> - Only one of the modes can be set on a single user per channel
>
>
>
> Regards,
> Aragon
> ------------------------------------------------------------------
> To unsubscribe or change your subscription options, visit:
> http://www.ircservices.za.net/mailman/listinfo/ircservices-coding
>

----------------------------------------------------------------------------
Russ Garrett                                             russ at garrett.co.uk.
                                                  http://russ.garrett.co.uk.