--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [IRCServices] Is there a timeline in the future for supporting
+ ircd2.9 or greater
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <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">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="003068.html">
+ <LINK REL="Next" HREF="003073.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[IRCServices] Is there a timeline in the future for supporting
+ ircd2.9 or greater</H1>
+ <B>Finny Merrill</B>
+ <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"
+ TITLE="[IRCServices] Is there a timeline in the future for supporting
+ ircd2.9 or greater">griever at t2n.org
+ </A><BR>
+ <I>Tue Aug 20 15:18:00 PDT 2002</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="003068.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
+</A></li>
+ <LI>Next message: <A HREF="003073.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3070">[ date ]</a>
+ <a href="thread.html#3070">[ thread ]</a>
+ <a href="subject.html#3070">[ subject ]</a>
+ <a href="author.html#3070">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Tue, 20 Aug 2002, Andrew Church wrote:
+
+><i> >The WHY still remains the same, IETF-RFC should be the standard.
+</I>><i>
+</I>><i> For what it's worth, I agree with you 100%, and that's why I still
+</I>><i> have RFC1459 support in Services even though I'm pretty positive there
+</I>><i> are zero people out there using it. Now all you have to do is convince the
+</I>><i> users of the zillions of other ircds to conform to standards. Good luck.
+</I>><i> (See also the comments in my draft IRC protocol proposal at
+</I>><i> <A HREF="http://achurch.org/irc3/">http://achurch.org/irc3/</A> .)
+</I>
+He's not talking about RFC1459, he's talking about RFC2811-2813.
+
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="003068.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
+</A></li>
+ <LI>Next message: <A HREF="003073.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3070">[ date ]</a>
+ <a href="thread.html#3070">[ thread ]</a>
+ <a href="subject.html#3070">[ subject ]</a>
+ <a href="author.html#3070">[ author ]</a>
+ </LI>
+ </UL>
+
+</body></html>