[IRCServices Coding] ChanServ Mode Bug?
Finny Merrill
griever at t2n.org
Fri Sep 6 14:38:44 PDT 2002
On Fri, 6 Sep 2002, Arathorn wrote:
> I can confirm that under Unreal 3.1.4 that when having given myself a mode
> on a channel of +q (using /mode whilst opered):
>
> /oper Arathorn password
> /mode #channel +q Arathorn
> (in the #channel window in mIRC: )
> *** Arathorn sets mode: +q Arathorn
>
> on subsequently deopering and #channel -o, I can still modify the channel op
> list using /mode #channel +/-o.
>
> /mode Arathorn -o
> /mode #channel -o Arathorn
> *** Arathorn sets mode: -o Arathorn
> /mode #channel +o lurk
> *** Arathorn sets mode: +o lurk
> /mode #channel -o lurk
> *** Arathorn sets mode: -o lurk
> /mode #channel -q Arathorn
> *** Arathorn sets mode: -q Arathorn
> /mode #channel +o lurk
> *** Arathorn: you're not channel operator
>
> On subsequently taking off the +q channel mode, as you can see, i can no
> longer op/deop people.
> When trying a /mode Arathorn +q when non-opered, i get
>
> #staff Only servers can change that mode
>
> Now, I may be restating the patently obvious here - and I'm not entirely
> sure how this impacts IRCServices, given that I believed that a channel
> usermode of +q was intended to indicate Channel Founder by services (at
> least, this is how it seems to work for me on Unreal 3.1.*/services
> 4.5.38+) - and thus should only effect one user (the founder) at a time. And
> I'm not the channel founder for #channel, in the above example, either. On
> 3.1.3 I don't think I was able to /mode #channel Arathorn +q (when opered),
> however - so something seems to have changed somewhere along the line for
> 3.1.4
>
> Hope is of vague help;
>
> A.
> _______________________
> arathorn at theonering.net
> cosysadmin, TheOneRing.net
>
+q does not give you +o privs
anyone can be +qed