]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/002492.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 002492.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Thoughts on 433 numeric?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Thoughts%20on%20433%20numeric%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="002491.html">
11 <LINK REL="Next" HREF="002495.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Thoughts on 433 numeric?</H1>
15 <B>Ben Goldstein</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Thoughts%20on%20433%20numeric%3F&In-Reply-To="
17 TITLE="[IRCServices] Thoughts on 433 numeric?">beng at nc.rr.com
18 </A><BR>
19 <I>Mon Nov 12 01:17:00 PST 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002491.html">[IRCServices] Thoughts on 433 numeric?
22 </A></li>
23 <LI>Next message: <A HREF="002495.html">[IRCServices] Thoughts on 433 numeric?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2492">[ date ]</a>
27 <a href="thread.html#2492">[ thread ]</a>
28 <a href="subject.html#2492">[ subject ]</a>
29 <a href="author.html#2492">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i> &gt;&gt;About the only problem I've found with it is if I have kill set to quick
35 </I>&gt;<i> &gt;&gt;and access the nick from a <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">user at host</A> not in the access list, services
36 </I>&gt;<i> &gt;&gt;sends the numeric as soon as I connect... not a big problem, unless the
37 </I>&gt;<i> &gt;&gt;IRC client is one that changes nicks automatically when it receives that
38 </I>&gt;<i> &gt;&gt;numeric. :)
39 </I>&gt;<i> &gt;
40 </I>&gt;<i> &gt; Do you think, say, 10 seconds before the kill/SVSNICK would be long
41 </I>&gt;<i> &gt;enough? Otherwise I don't see a way to solve this without, say, creating
42 </I>&gt;<i> &gt;an all-new numeric or some such...
43 </I>
44 I've noticed services sends 433 on NickServ's initial warning. What would
45 be ideal is if services sent the numeric 20 seconds or so before the
46 SVSNICK. The pros to keeping numeric 433 is if the client is one that
47 changes nicks to avoid the collide. This is only good behavior if the
48 numeric is sent shortly before the collide, however.
49
50 &gt;<i> To follow up on this--what would people think of taking a currently
51 </I>&gt;<i> unused numeric, say 430, and using it for &quot;nick registered/forbidden&quot;?
52 </I>&gt;<i> That way we get the advantage of keeping bots RFC-compliant without the
53 </I>&gt;<i> problems of people getting confused by &quot;nick in use&quot; messages.
54 </I>
55 As long as the numeric is not sent initially, but shortly before the
56 kill/svsnick, this shouldn't be an issue.
57
58 -- Ben Goldstein
59
60
61
62 </PRE>
63
64 <!--endarticle-->
65 <HR>
66 <P><UL>
67 <!--threads-->
68 <LI>Previous message: <A HREF="002491.html">[IRCServices] Thoughts on 433 numeric?
69 </A></li>
70 <LI>Next message: <A HREF="002495.html">[IRCServices] Thoughts on 433 numeric?
71 </A></li>
72 <LI> <B>Messages sorted by:</B>
73 <a href="date.html#2492">[ date ]</a>
74 <a href="thread.html#2492">[ thread ]</a>
75 <a href="subject.html#2492">[ subject ]</a>
76 <a href="author.html#2492">[ author ]</a>
77 </LI>
78 </UL>
79
80 </body></html>