projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
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="002437.html"> | |
| 11 | <LINK REL="Next" HREF="002438.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices] Query on ChanServ/Nickserv behavior</H1> | |
| 15 | <B>Andrew Church</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">achurch at achurch.org | |
| 18 | </A><BR> | |
| 19 | <I>Fri Nov 2 07:16:05 PST 2001</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="002437.html">[IRCServices] Query on ChanServ/Nickserv behavior | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="002438.html">[IRCServices] Linking - Problem | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#2435">[ date ]</a> | |
| 27 | <a href="thread.html#2435">[ thread ]</a> | |
| 28 | <a href="subject.html#2435">[ subject ]</a> | |
| 29 | <a href="author.html#2435">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>>><i> This has been requested by a number of people and is being considered. | |
| 35 | </I>>><i>(On the other hand, as long as you send /ns identify first this won't be a | |
| 36 | </I>>><i>problem...) | |
| 37 | </I>><i> | |
| 38 | </I>><i>Ah, problem is the IRCd responds quicker than Services, so a list of | |
| 39 | </I>><i>commands in a connection script can - and usually do - get | |
| 40 | </I>><i>re-ordered. This is true even on a single-server network, and is | |
| 41 | </I>><i>presumably much worse on a lagged multi-server network. | |
| 42 | </I> | |
| 43 | But remember that the join itself has to propogate to Services, and | |
| 44 | since the ircd doesn't see the join until after the PRIVMSG to identify, | |
| 45 | Services should also get them in the same order. (If not, it's an ircd | |
| 46 | bug.) | |
| 47 | ||
| 48 | --Andrew Church | |
| 49 | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
| 50 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 51 | ||
| 52 | </PRE> | |
| 53 | ||
| 54 | <!--endarticle--> | |
| 55 | <HR> | |
| 56 | <P><UL> | |
| 57 | <!--threads--> | |
| 58 | <LI>Previous message: <A HREF="002437.html">[IRCServices] Query on ChanServ/Nickserv behavior | |
| 59 | </A></li> | |
| 60 | <LI>Next message: <A HREF="002438.html">[IRCServices] Linking - Problem | |
| 61 | </A></li> | |
| 62 | <LI> <B>Messages sorted by:</B> | |
| 63 | <a href="date.html#2435">[ date ]</a> | |
| 64 | <a href="thread.html#2435">[ thread ]</a> | |
| 65 | <a href="subject.html#2435">[ subject ]</a> | |
| 66 | <a href="author.html#2435">[ author ]</a> | |
| 67 | </LI> | |
| 68 | </UL> | |
| 69 | ||
| 70 | </body></html> |