software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/002436.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=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002434.html">
  11    <LINK REL="Next"  HREF="002437.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Query on ChanServ/Nickserv behavior</H1>
  15     <B>Trevor Talbot</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Query%20on%20ChanServ/Nickserv%20behavior&In-Reply-To="
  17        TITLE="[IRCServices] Query on ChanServ/Nickserv behavior">quension at softhome.net
  18        </A><BR>
  19     <I>Fri Nov  2 07:34:00 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002434.html">[IRCServices] Query on ChanServ/Nickserv behavior
  22 </A></li>
  23         <LI>Next message: <A HREF="002437.html">[IRCServices] Query on ChanServ/Nickserv behavior
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2436">[ date ]</a>
  27               <a href="thread.html#2436">[ thread ]</a>
  28               <a href="subject.html#2436">[ subject ]</a>
  29               <a href="author.html#2436">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Jonathan Morton wrote:
  35
  36 &gt;<i> &gt;  &gt;Related to this, I'd rather like an option to be opped on my channels
  37 </I>&gt;<i> &gt;&gt;as soon as I *have* identified, rather than having to issue OP
  38 </I>&gt;<i> &gt;&gt;commands just because the JOIN command beat my IDENTIFY command
  39 </I>&gt;<i> &gt;&gt;through the post.
  40 </I>&gt;<i> &gt;
  41 </I>&gt;<i> &gt;      This has been requested by a number of people and is being considered.
  42 </I>&gt;<i> &gt;(On the other hand, as long as you send /ns identify first this won't be a
  43 </I>&gt;<i> &gt;problem...)
  44 </I>&gt;<i>
  45 </I>&gt;<i> Ah, problem is the IRCd responds quicker than Services, so a list of
  46 </I>&gt;<i> commands in a connection script can - and usually do - get
  47 </I>&gt;<i> re-ordered.  This is true even on a single-server network, and is
  48 </I>&gt;<i> presumably much worse on a lagged multi-server network.
  49 </I>
  50 Reordered?  Sounds like a client issue.
  51
  52 If the client sends the identify command before the join command, services
  53 will work as expected.  Since services is delayed, there's no reason it
  54 would see the join _before_ the identify.
  55
  56 -- Quension
  57
  58 </PRE>
  59
  60 <!--endarticle-->
  61     <HR>
  62     <P><UL>
  63         <!--threads-->
  64         <LI>Previous message: <A HREF="002434.html">[IRCServices] Query on ChanServ/Nickserv behavior
  65 </A></li>
  66         <LI>Next message: <A HREF="002437.html">[IRCServices] Query on ChanServ/Nickserv behavior
  67 </A></li>
  68          <LI> <B>Messages sorted by:</B>
  69               <a href="date.html#2436">[ date ]</a>
  70               <a href="thread.html#2436">[ thread ]</a>
  71               <a href="subject.html#2436">[ subject ]</a>
  72               <a href="author.html#2436">[ author ]</a>
  73          </LI>
  74        </UL>
  75
  76 </body></html>