software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001482.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Services Suggestion - NickServ
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20Suggestion%20-%20NickServ&In-Reply-To=NDBBKLOOKLMAKHFICBLCGELJEIAA.uhc0%40rz.uni-karlsruhe.de">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001481.html">
  11    <LINK REL="Next"  HREF="001475.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Services Suggestion - NickServ</H1>
  15     <B>Mark Hetherington (Eurocom)</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20Suggestion%20-%20NickServ&In-Reply-To=NDBBKLOOKLMAKHFICBLCGELJEIAA.uhc0%40rz.uni-karlsruhe.de"
  17        TITLE="[IRCServices] Services Suggestion - NickServ">markh at eurodltd.co.uk
  18        </A><BR>
  19     <I>Fri Feb 23 01:44:01 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001481.html">AW: [IRCServices] Services Suggestion - NickServ
  22 </A></li>
  23         <LI>Next message: <A HREF="001475.html">[IRCServices] Services 4.5.2 released
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1482">[ date ]</a>
  27               <a href="thread.html#1482">[ thread ]</a>
  28               <a href="subject.html#1482">[ subject ]</a>
  29               <a href="author.html#1482">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Hi,
  35
  36 I think you may have misinterpreted my original comments as relating to IRCd
  37 when they relate to the behaviour of a Java client which is integrated most
  38 commonly in a web site and gives visitors the opportunity to join IRC and a
  39 channel dedicated to the subject of the web site.
  40
  41 &gt;<i> Still not convinced, why my computer should use cpu time to
  42 </I>&gt;<i> check nicknames for possible guestnick suffices,
  43 </I>
  44 As with other features of services which may affect performance, there is
  45 little coding overhead in making it optional at either compile or
  46 configuration time. e.g. Session limiting and Statserv.
  47
  48 &gt;<i> while I do not have any java daemon connected.
  49 </I>&gt;<i> Will you tell me, that you CAN take the risk of using a
  50 </I>&gt;<i> non-opensource daemon
  51 </I>&gt;<i> on your network, and still want support for that in an opensource
  52 </I>&gt;<i> project ?
  53 </I>
  54 It is a client not a daemon.
  55
  56 I use a modified version of Unreal as my ircd across the network and am in
  57 the process of developing an IRCd from the ground up. I would never dream of
  58 using a pre compiled binary or a java ircd.
  59
  60 &gt;<i> How will you know, that this specific daemon does not make
  61 </I>&gt;<i> additional connections
  62 </I>&gt;<i> do abnormal destinations like
  63 </I>&gt;<i> I-am-here-to-collect-nickname-passwords.com ?
  64 </I>&gt;<i> I still believe, that it is specific to your network, and others
  65 </I>&gt;<i> where people
  66 </I>&gt;<i> do not have the time to write their own daemon, but instead use
  67 </I>&gt;<i> precompiled
  68 </I>&gt;<i> binaries.
  69 </I>
  70 It is a client used by users. The fear you express as to the collection of
  71 passwords could be just as easily applied to any piece of software. It is
  72 the users which are ultimately responsible for their personal security, we
  73 can only advise them as to course of actions wrt potential security problems
  74 since the client is outside of our control and assist them in securing their
  75 IRC related activities.
  76
  77 &gt;<i> If I cannot see the source of that particular software, I cannot risk
  78 </I>&gt;<i> letting many people use that.
  79 </I>&gt;<i> Nor I can risk to add support for a behavior
  80 </I>&gt;<i> evolved by the usage of it. I would not code support for something I see,
  81 </I>
  82 I have not seen the source to MIRC... should I ban that from the network or
  83 remove the workarounds for the MIRC &quot;status bug&quot; from the IRCd? This may
  84 stem from a potential misunderstanding and I do not advocate supporting
  85 specifics per client since this is obviously the wrong way to go. However,
  86 when a group of clients from different sources share a common theme, it
  87 seems reasonable to implement some form of services that cater to their
  88 needs.
  89
  90 &gt;<i> Those areas are already grayed out, at the moment Mr. Church decided to
  91 </I>&gt;<i> support Unreal. But the tone of the gray you are suggesting is simply too
  92 </I>&gt;<i> similar to white, just to express it in your words.
  93 </I>
  94 Personally I am glad to see there will be native support for Unreal in
  95 services. It saves using patches to add the support required so makes
  96 services available to a wider IRCd audience. Unreal seems to be avoided by
  97 some people but I have yet to see reasons mentioned for this but it does
  98 seem to go beyond a mere personal taste issue wrt IRCd. But I guess that
  99 discussion is beyond the scope of this list :)
 100
 101
 102 Mark.
 103 CTCP Networks.
 104
 105
 106
 107 </PRE>
 108
 109 <!--endarticle-->
 110     <HR>
 111     <P><UL>
 112         <!--threads-->
 113         <LI>Previous message: <A HREF="001481.html">AW: [IRCServices] Services Suggestion - NickServ
 114 </A></li>
 115         <LI>Next message: <A HREF="001475.html">[IRCServices] Services 4.5.2 released
 116 </A></li>
 117          <LI> <B>Messages sorted by:</B>
 118               <a href="date.html#1482">[ date ]</a>
 119               <a href="thread.html#1482">[ thread ]</a>
 120               <a href="subject.html#1482">[ subject ]</a>
 121               <a href="author.html#1482">[ author ]</a>
 122          </LI>
 123        </UL>
 124
 125 </body></html>