]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/002429.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 002429.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Query on ChanServ/Nickserv behavior
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Query%20on%20ChanServ/Nickserv%20behavior&In-Reply-To=Pine.LNX.4.30.0111011743330.10379-100000%40foxbox.kittyfox.net">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="002428.html">
11 <LINK REL="Next" HREF="002433.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Query on ChanServ/Nickserv behavior</H1>
15 <B>Jonathan Morton</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Query%20on%20ChanServ/Nickserv%20behavior&In-Reply-To=Pine.LNX.4.30.0111011743330.10379-100000%40foxbox.kittyfox.net"
17 TITLE="[IRCServices] Query on ChanServ/Nickserv behavior">chromi at cyberspace.org
18 </A><BR>
19 <I>Fri Nov 2 01:52:00 PST 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002428.html">[IRCServices] Query on ChanServ/Nickserv behavior
22 </A></li>
23 <LI>Next message: <A HREF="002433.html">[IRCServices] Query on ChanServ/Nickserv behavior
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2429">[ date ]</a>
27 <a href="thread.html#2429">[ thread ]</a>
28 <a href="subject.html#2429">[ subject ]</a>
29 <a href="author.html#2429">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i>I find this behavior rather odd. Am I misunderstanding the purpose of
35 </I>&gt;<i>being able to turn Secure off for NickServ? The Help states &quot;with SECURE
36 </I>&gt;<i>set, you must enter your password before you will be recognized as the
37 </I>&gt;<i>owner of the nick, regardless of whether your address is on the access
38 </I>&gt;<i>list.&quot; This implies to me that if SECURE is NOT set, then NickServ will
39 </I>&gt;<i>examine the access list and, if it should find a match, let ChanServ know
40 </I>&gt;<i>that you're okay to op as you've been &quot;implicitly identified.&quot;
41 </I>
42 ChanServ will not op you unless you have used IDENTIFY. Period.
43
44 Related to this, I'd rather like an option to be opped on my channels
45 as soon as I *have* identified, rather than having to issue OP
46 commands just because the JOIN command beat my IDENTIFY command
47 through the post.
48
49 --
50 --------------------------------------------------------------
51 from: Jonathan &quot;Chromatix&quot; Morton
52 mail: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">chromi at cyberspace.org</A> (not for attachments)
53 website: <A HREF="http://www.chromatix.uklinux.net/vnc/">http://www.chromatix.uklinux.net/vnc/</A>
54 geekcode: GCS$/E dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$
55 V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
56 tagline: The key to knowledge is not to rely on people to teach you it.
57
58 </PRE>
59
60 <!--endarticle-->
61 <HR>
62 <P><UL>
63 <!--threads-->
64 <LI>Previous message: <A HREF="002428.html">[IRCServices] Query on ChanServ/Nickserv behavior
65 </A></li>
66 <LI>Next message: <A HREF="002433.html">[IRCServices] Query on ChanServ/Nickserv behavior
67 </A></li>
68 <LI> <B>Messages sorted by:</B>
69 <a href="date.html#2429">[ date ]</a>
70 <a href="thread.html#2429">[ thread ]</a>
71 <a href="subject.html#2429">[ subject ]</a>
72 <a href="author.html#2429">[ author ]</a>
73 </LI>
74 </UL>
75
76 </body></html>