]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2007/005458.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2007 / 005458.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] ChanServ does not add NickServ noop to ChanServ
5 NeverOp
6 </TITLE>
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=46E9BCB0.1030105%40fastmail.com.au">
9 <META NAME="robots" CONTENT="index,nofollow">
10 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
11 <LINK REL="Previous" HREF="005448.html">
12 <LINK REL="Next" HREF="005453.html">
13 </HEAD>
14 <BODY BGCOLOR="#ffffff">
15 <H1>[IRCServices] ChanServ does not add NickServ noop to ChanServ
16 NeverOp</H1>
17 <B>Kieron Thwaites</B>
18 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20does%20not%20add%20NickServ%20noop%20to%20ChanServ%0A%09NeverOp&In-Reply-To=46E9BCB0.1030105%40fastmail.com.au"
19 TITLE="[IRCServices] ChanServ does not add NickServ noop to ChanServ
20 NeverOp">ron2k.za at gmail.com
21 </A><BR>
22 <I>Thu Sep 13 23:02:10 PDT 2007</I>
23 <P><UL>
24 <LI>Previous message: <A HREF="005448.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
25 NeverOp
26 </A></li>
27 <LI>Next message: <A HREF="005453.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
28 NeverOp
29 </A></li>
30 <LI> <B>Messages sorted by:</B>
31 <a href="date.html#5458">[ date ]</a>
32 <a href="thread.html#5458">[ thread ]</a>
33 <a href="subject.html#5458">[ subject ]</a>
34 <a href="author.html#5458">[ author ]</a>
35 </LI>
36 </UL>
37 <HR>
38 <!--beginarticle-->
39 <PRE>I don't think it really matters. Whether the user has NickServ NOOP or
40 is on the ChanServ NOP list, the effect is the same - the nick will
41 not receive channel operator status.
42
43 On the other hand, it could be useful to add NOOP users to the
44 ChanServ NOP list, in the event of a user removing his NOOP status at
45 a later stage.
46
47 (Interesting thought - I wonder if the ACCESS command has the same
48 restrictions? I'll play around with it this evening.)
49
50 --K
51
52 On 14/09/2007, Casey &lt;<A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">caseyclaydon at fastmail.com.au</A>&gt; wrote:
53 &gt;<i> With NickServ noop on - ChanServ does not add NickServ noop to ChanServ
54 </I>&gt;<i> NeverOp
55 </I>&gt;<i>
56 </I>&gt;<i>
57 </I>&gt;<i> -ChanServ- Maintains the NeverOp (NOP) list for a channel. Users with
58 </I>&gt;<i> -ChanServ- NOP status are not permitted to be given channel operator
59 </I>&gt;<i> -ChanServ- (mode +o) status, and ChanServ will remove mode +o from such
60 </I>&gt;<i> -ChanServ- users whenever it is given to them.
61 </I>&gt;<i>
62 </I>&gt;<i>
63 </I>&gt;<i> NickServ noop should be allowed to be added to ChanServ NeverOp
64 </I>&gt;<i> ------------------------------------------------------------------
65 </I>&gt;<i> To unsubscribe or change your subscription options, visit:
66 </I>&gt;<i> <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices</A>
67 </I>&gt;<i>
68 </I></PRE>
69
70
71 <!--endarticle-->
72 <HR>
73 <P><UL>
74 <!--threads-->
75 <LI>Previous message: <A HREF="005448.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
76 NeverOp
77 </A></li>
78 <LI>Next message: <A HREF="005453.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
79 NeverOp
80 </A></li>
81 <LI> <B>Messages sorted by:</B>
82 <a href="date.html#5458">[ date ]</a>
83 <a href="thread.html#5458">[ thread ]</a>
84 <a href="subject.html#5458">[ subject ]</a>
85 <a href="author.html#5458">[ author ]</a>
86 </LI>
87 </UL>
88
89 </body></html>