--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [IRCServices] Query on ChanServ/Nickserv behavior
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Query%20on%20ChanServ/Nickserv%20behavior&In-Reply-To=3BE23015.EB558E2E%40softhome.net">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002436.html">
+ <LINK REL="Next" HREF="002435.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[IRCServices] Query on ChanServ/Nickserv behavior</H1>
+ <B>Jonathan Morton</B>
+ <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Query%20on%20ChanServ/Nickserv%20behavior&In-Reply-To=3BE23015.EB558E2E%40softhome.net"
+ TITLE="[IRCServices] Query on ChanServ/Nickserv behavior">chromi at cyberspace.org
+ </A><BR>
+ <I>Fri Nov 2 08:25:08 PST 2001</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002436.html">[IRCServices] Query on ChanServ/Nickserv behavior
+</A></li>
+ <LI>Next message: <A HREF="002435.html">[IRCServices] Query on ChanServ/Nickserv behavior
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2437">[ date ]</a>
+ <a href="thread.html#2437">[ thread ]</a>
+ <a href="subject.html#2437">[ subject ]</a>
+ <a href="author.html#2437">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>><i> > > >Related to this, I'd rather like an option to be opped on my channels
+</I>>><i> >>as soon as I *have* identified, rather than having to issue OP
+</I>>><i> >>commands just because the JOIN command beat my IDENTIFY command
+</I>>><i> >>through the post.
+</I>>><i> >
+</I>>><i> > This has been requested by a number of people and is being
+</I>>><i>considered.
+</I>>><i> >(On the other hand, as long as you send /ns identify first this won't be a
+</I>>><i> >problem...)
+</I>>><i>
+</I>>><i> Ah, problem is the IRCd responds quicker than Services, so a list of
+</I>>><i> commands in a connection script can - and usually do - get
+</I>>><i> re-ordered. This is true even on a single-server network, and is
+</I>>><i> presumably much worse on a lagged multi-server network.
+</I>><i>
+</I>><i>Reordered? Sounds like a client issue.
+</I>><i>
+</I>><i>If the client sends the identify command before the join command, services
+</I>><i>will work as expected. Since services is delayed, there's no reason it
+</I>><i>would see the join _before_ the identify.
+</I>
+Seen using two completely different clients - Ircle and X-Chat.
+
+--
+--------------------------------------------------------------
+from: Jonathan "Chromatix" Morton
+mail: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">chromi at cyberspace.org</A> (not for attachments)
+website: <A HREF="http://www.chromatix.uklinux.net/vnc/">http://www.chromatix.uklinux.net/vnc/</A>
+geekcode: GCS$/E dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$
+ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
+tagline: The key to knowledge is not to rely on people to teach you it.
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002436.html">[IRCServices] Query on ChanServ/Nickserv behavior
+</A></li>
+ <LI>Next message: <A HREF="002435.html">[IRCServices] Query on ChanServ/Nickserv behavior
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2437">[ date ]</a>
+ <a href="thread.html#2437">[ thread ]</a>
+ <a href="subject.html#2437">[ subject ]</a>
+ <a href="author.html#2437">[ author ]</a>
+ </LI>
+ </UL>
+
+</body></html>
projects / irc.git / blobdiff