]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/003070.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 003070.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Is there a timeline in the future for supporting
5 ircd2.9 or greater
6 </TITLE>
7 <LINK REL="Index" HREF="index.html" >
8 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Is%20there%20a%20timeline%20in%20the%20future%20for%20supporting%0A%20ircd2.9%20or%20greater&In-Reply-To=3d623618.15237%40achurch.org">
9 <META NAME="robots" CONTENT="index,nofollow">
10 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
11 <LINK REL="Previous" HREF="003068.html">
12 <LINK REL="Next" HREF="003073.html">
13 </HEAD>
14 <BODY BGCOLOR="#ffffff">
15 <H1>[IRCServices] Is there a timeline in the future for supporting
16 ircd2.9 or greater</H1>
17 <B>Finny Merrill</B>
18 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Is%20there%20a%20timeline%20in%20the%20future%20for%20supporting%0A%20ircd2.9%20or%20greater&In-Reply-To=3d623618.15237%40achurch.org"
19 TITLE="[IRCServices] Is there a timeline in the future for supporting
20 ircd2.9 or greater">griever at t2n.org
21 </A><BR>
22 <I>Tue Aug 20 15:18:00 PDT 2002</I>
23 <P><UL>
24 <LI>Previous message: <A HREF="003068.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
25 </A></li>
26 <LI>Next message: <A HREF="003073.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
27 </A></li>
28 <LI> <B>Messages sorted by:</B>
29 <a href="date.html#3070">[ date ]</a>
30 <a href="thread.html#3070">[ thread ]</a>
31 <a href="subject.html#3070">[ subject ]</a>
32 <a href="author.html#3070">[ author ]</a>
33 </LI>
34 </UL>
35 <HR>
36 <!--beginarticle-->
37 <PRE>On Tue, 20 Aug 2002, Andrew Church wrote:
38
39 &gt;<i> &gt;The WHY still remains the same, IETF-RFC should be the standard.
40 </I>&gt;<i>
41 </I>&gt;<i> For what it's worth, I agree with you 100%, and that's why I still
42 </I>&gt;<i> have RFC1459 support in Services even though I'm pretty positive there
43 </I>&gt;<i> are zero people out there using it. Now all you have to do is convince the
44 </I>&gt;<i> users of the zillions of other ircds to conform to standards. Good luck.
45 </I>&gt;<i> (See also the comments in my draft IRC protocol proposal at
46 </I>&gt;<i> <A HREF="http://achurch.org/irc3/">http://achurch.org/irc3/</A> .)
47 </I>
48 He's not talking about RFC1459, he's talking about RFC2811-2813.
49
50
51 </PRE>
52
53 <!--endarticle-->
54 <HR>
55 <P><UL>
56 <!--threads-->
57 <LI>Previous message: <A HREF="003068.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
58 </A></li>
59 <LI>Next message: <A HREF="003073.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
60 </A></li>
61 <LI> <B>Messages sorted by:</B>
62 <a href="date.html#3070">[ date ]</a>
63 <a href="thread.html#3070">[ thread ]</a>
64 <a href="subject.html#3070">[ subject ]</a>
65 <a href="author.html#3070">[ author ]</a>
66 </LI>
67 </UL>
68
69 </body></html>