1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] ChanServ does not add NickServ noop to ChanServ
7 <LINK REL=
"Index" HREF=
"index.html" >
8 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20does%20not%20add%20NickServ%20noop%20to%20ChanServ%0A%09NeverOp&In-Reply-To=debb3bc0709132302mae7a62dwf4319cfbe1388541%40mail.gmail.com">
9 <META NAME=
"robots" CONTENT=
"index,nofollow">
10 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
11 <LINK REL=
"Previous" HREF=
"005458.html">
12 <LINK REL=
"Next" HREF=
"005447.html">
14 <BODY BGCOLOR=
"#ffffff">
15 <H1>[IRCServices] ChanServ does not add NickServ noop to ChanServ
18 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20does%20not%20add%20NickServ%20noop%20to%20ChanServ%0A%09NeverOp&In-Reply-To=debb3bc0709132302mae7a62dwf4319cfbe1388541%40mail.gmail.com"
19 TITLE=
"[IRCServices] ChanServ does not add NickServ noop to ChanServ
20 NeverOp">caseyclaydon at fastmail.com.au
22 <I>Thu Sep
13 23:
29:
10 PDT
2007</I>
24 <LI>Previous message:
<A HREF=
"005458.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
27 <LI>Next message:
<A HREF=
"005447.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
30 <LI> <B>Messages sorted by:
</B>
31 <a href=
"date.html#5453">[ date ]
</a>
32 <a href=
"thread.html#5453">[ thread ]
</a>
33 <a href=
"subject.html#5453">[ subject ]
</a>
34 <a href=
"author.html#5453">[ author ]
</a>
39 <PRE>When someone adds a person to the NeverOp list to not be given ops at
40 all when someone does +o / +h them.
42 someone who is on NickServ noop cannot be added to the NeverOp list.
46 Kieron Thwaites wrote:
47 ><i> I don't think it really matters. Whether the user has NickServ NOOP or
48 </I>><i> is on the ChanServ NOP list, the effect is the same - the nick will
49 </I>><i> not receive channel operator status.
51 </I>><i> On the other hand, it could be useful to add NOOP users to the
52 </I>><i> ChanServ NOP list, in the event of a user removing his NOOP status at
53 </I>><i> a later stage.
55 </I>><i> (Interesting thought - I wonder if the ACCESS command has the same
56 </I>><i> restrictions? I'll play around with it this evening.)
60 </I>><i> On
14/
09/
2007, Casey
<<A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">caseyclaydon at fastmail.com.au
</A>> wrote:
62 </I>>><i> With NickServ noop on - ChanServ does not add NickServ noop to ChanServ
63 </I>>><i> NeverOp
66 </I>>><i> -ChanServ- Maintains the NeverOp (NOP) list for a channel. Users with
67 </I>>><i> -ChanServ- NOP status are not permitted to be given channel operator
68 </I>>><i> -ChanServ- (mode +o) status, and ChanServ will remove mode +o from such
69 </I>>><i> -ChanServ- users whenever it is given to them.
72 </I>>><i> NickServ noop should be allowed to be added to ChanServ NeverOp
73 </I>>><i> ------------------------------------------------------------------
74 </I>>><i> To unsubscribe or change your subscription options, visit:
75 </I>>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices
</A>
78 </I>><i> ------------------------------------------------------------------
79 </I>><i> To unsubscribe or change your subscription options, visit:
80 </I>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices
</A>
92 <LI>Previous message:
<A HREF=
"005458.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
95 <LI>Next message:
<A HREF=
"005447.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
98 <LI> <B>Messages sorted by:
</B>
99 <a href=
"date.html#5453">[ date ]
</a>
100 <a href=
"thread.html#5453">[ thread ]
</a>
101 <a href=
"subject.html#5453">[ subject ]
</a>
102 <a href=
"author.html#5453">[ author ]
</a>