]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001386.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 001386.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] ChanServ Mode Bug?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ChanServ%20Mode%20Bug%3F&In-Reply-To=">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001390.html">
11 <LINK REL="Next" HREF="001403.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] ChanServ Mode Bug?</H1>
15 <B>M</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ChanServ%20Mode%20Bug%3F&In-Reply-To="
17 TITLE="[IRCServices Coding] ChanServ Mode Bug?">mark at ctcp.net
18 </A><BR>
19 <I>Fri Sep 6 16:18:01 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001390.html">[IRCServices Coding] ChanServ Mode Bug?
22 </A></li>
23 <LI>Next message: <A HREF="001403.html">[IRCServices Coding] cygwin tools error..
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1386">[ date ]</a>
27 <a href="thread.html#1386">[ thread ]</a>
28 <a href="subject.html#1386">[ subject ]</a>
29 <a href="author.html#1386">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Arathorn wrote:
35 &gt;<i> The whole point of my 'test' was that after initially opering up
36 </I>&gt;<i> in order to
37 </I>&gt;<i> set #channel +q Arathorn - i promptly deopered (with /mode
38 </I>&gt;<i> Arathorn -o). Or
39 </I>&gt;<i> does that still count as being 'opered'?
40 </I>&gt;<i>
41 </I>&gt;<i> Anyway, on repeating the whole exercise whilst *not opered* (and
42 </I>&gt;<i> never have
43 </I>&gt;<i> been opered that session) - i.e. registering a new channel to gain founder
44 </I>&gt;<i> status (and thus also +q on join), precisely the same behaviour
45 </I>&gt;<i> is observed.
46 </I>&gt;<i> I can deop, but whilst I still am +q on the channel, I can op and deop any
47 </I>&gt;<i> other user. I repeat - at no point in any of that was I opered.
48 </I>&gt;<i>
49 </I>&gt;<i> Please read the whole mail next time before feeling the need to shoot it
50 </I>&gt;<i> down in flames; I was after all just trying to provide Andrew with the
51 </I>&gt;<i> confirmation he requested. This behaviour doesn't pose any problem in my
52 </I>&gt;<i> configuration, at any rate.
53 </I>
54 I did read your whole post and your /mode -o will not necessarily fully
55 deoper you. Since that is all you did, I stand by my previous post.
56
57 I would refer you to my other post, a post from a member of the Unreal
58 team and the source code for Unreal to confirm the designed behaviour of
59 +q.
60
61 M.
62
63
64
65 </PRE>
66
67 <!--endarticle-->
68 <HR>
69 <P><UL>
70 <!--threads-->
71 <LI>Previous message: <A HREF="001390.html">[IRCServices Coding] ChanServ Mode Bug?
72 </A></li>
73 <LI>Next message: <A HREF="001403.html">[IRCServices Coding] cygwin tools error..
74 </A></li>
75 <LI> <B>Messages sorted by:</B>
76 <a href="date.html#1386">[ date ]</a>
77 <a href="thread.html#1386">[ thread ]</a>
78 <a href="subject.html#1386">[ subject ]</a>
79 <a href="author.html#1386">[ author ]</a>
80 </LI>
81 </UL>
82
83 </body></html>