software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/002759.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Which route to take - Module?
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Which%20route%20to%20take%20-%20Module%3F&In-Reply-To=3F57A0BA.9080909%40t2n.org">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002203.html">
  11    <LINK REL="Next"  HREF="002755.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Which route to take - Module?</H1>
  15     <B>Trevor Talbot</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Which%20route%20to%20take%20-%20Module%3F&In-Reply-To=3F57A0BA.9080909%40t2n.org"
  17        TITLE="[IRCServices Coding] Which route to take - Module?">quension at mac.com
  18        </A><BR>
  19     <I>Thu Sep  4 13:54:21 PDT 2003</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002203.html">[IRCServices Coding] Which route to take - Module?
  22 </A></li>
  23         <LI>Next message: <A HREF="002755.html">[IRCServices Coding] Which route to take - Module?
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2759">[ date ]</a>
  27               <a href="thread.html#2759">[ thread ]</a>
  28               <a href="subject.html#2759">[ subject ]</a>
  29               <a href="author.html#2759">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>On Thursday, Sep 4, 2003, at 13:29 US/Pacific, Robert F Merrill wrote:
  35
  36 &gt;<i> Brent DiNicola wrote:
  37 </I>&gt;<i>
  38 </I>&gt;&gt;<i> It wasn't an easy subject to sum up in just a few words.
  39 </I>
  40 [...]
  41
  42 &gt;<i> Services is not the place to fix broken clients, and any client which
  43 </I>&gt;<i> doesn't display notices correctly is broken. If someone wants to see
  44 </I>&gt;<i> notices differently, they can either a) change their client or in the
  45 </I>&gt;<i> case of webtv b) change the ircd
  46 </I>&gt;<i>
  47 </I>&gt;<i> services is the wrong thing to change
  48 </I>
  49 And telling someone what they obviously already know is generally not a
  50 good idea.  Especially when they spent a very long paragraph defending
  51 their decision in the first place.
  52
  53 This is the coding list, not the feature request list.  He asked for
  54 code design approaches, not for political insight.
  55
  56 -- Quension
  57
  58
  59 </PRE>
  60
  61 <!--endarticle-->
  62     <HR>
  63     <P><UL>
  64         <!--threads-->
  65         <LI>Previous message: <A HREF="002203.html">[IRCServices Coding] Which route to take - Module?
  66 </A></li>
  67         <LI>Next message: <A HREF="002755.html">[IRCServices Coding] Which route to take - Module?
  68 </A></li>
  69          <LI> <B>Messages sorted by:</B>
  70               <a href="date.html#2759">[ date ]</a>
  71               <a href="thread.html#2759">[ thread ]</a>
  72               <a href="subject.html#2759">[ subject ]</a>
  73               <a href="author.html#2759">[ author ]</a>
  74          </LI>
  75        </UL>
  76
  77 </body></html>