software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000271.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] More bugs and suggestions for Version 5.0
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20More%20bugs%20and%20suggestions%20for%20Version%205.0&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="000270.html">
  11    <LINK REL="Next"  HREF="000272.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] More bugs and suggestions for Version 5.0</H1>
  15     <B>Andrew Kempe</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20More%20bugs%20and%20suggestions%20for%20Version%205.0&In-Reply-To="
  17        TITLE="[IRCServices Coding] More bugs and suggestions for Version 5.0">andrewk at isdial.net
  18        </A><BR>
  19     <I>Thu Feb 14 00:52:23 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000270.html">[IRCServices Coding] More bugs and suggestions for Version 5.0
  22 </A></li>
  23         <LI>Next message: <A HREF="000272.html">[IRCServices Coding] lists
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#271">[ date ]</a>
  27               <a href="thread.html#271">[ thread ]</a>
  28               <a href="subject.html#271">[ subject ]</a>
  29               <a href="author.html#271">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Comments are inline...
  35
  36 &gt;<i> 8) Bug - either in text or operation - /cs help suspend produces the
  37 </I>&gt;<i> following information:
  38 </I>&gt;<i> -ChanServ- Unlike a forbidden channel, a suspended one does not
  39 </I>&gt;<i> -ChanServ- lose its information and will expire!
  40 </I>[snip]
  41 &gt;<i> version 4.5.x series as well as version 5 since the channels I have
  42 </I>noticed
  43 &gt;<i> it on were originally suspended under a version of 4.5.x and remained
  44 </I>&gt;<i> unexpired after migrating to 5.0.
  45 </I>
  46 Do these nicknames expire on the 4.5.x branch?
  47
  48 What is the output of: /ns info &lt;nick&gt; ALL
  49 This should either indicate the expiration date/time or &quot;does not expire&quot;.
  50
  51 Please can you confirm the setting in your config file regarding default
  52 expiration times for suspended nicks. (both in 4.5.x and 5.x)
  53
  54 &gt;<i> 9) Suggested config option to limit guest nick length. The new guest nicks
  55 </I>&gt;<i> can end up using a full 9 digit precision depending on IRCd limits which
  56 </I>on
  57 &gt;<i> smaller networks makes them seem a little excessive. It would be nice if
  58 </I>&gt;<i> there was a configuration ption to limit this. Obviously such option would
  59 </I>&gt;<i> have to be accompanied by information on the minimum length requirement.
  60 </I>
  61 The ID is not a simple number. A simple counter would be too easy to predict
  62 making it possible to collide nicks off the network. The current algorithm
  63 uses a counter and the time to generate the ID. This results in a very big
  64 number. So basically, a new algorithm needs to be used if you want to make
  65 the length of the guest ID shorter.
  66
  67 &gt;<i> 10) Suggestion wrt IDENTIFY command: Although generally I have not found
  68 </I>&gt;<i> any reasons to consider or suggest aliases for existing services commands
  69 </I>&gt;<i> since they can generally be scripted client side and merely add confusion
  70 </I>&gt;<i> to the command list, I have found one &quot;alias&quot; that I do implement within
  71 </I>[snip]
  72 &gt;<i> The other maybe less obvious benefit is less typing for people like myself
  73 </I>&gt;<i> that avoid scripts and automatic identification. :)
  74 </I>
  75 If you have one alias, more will follow. This just clutters up Services as
  76 more people hack the aliases to their own liking. Over time it will become
  77 more and more difficult to have a common set of commands. Support also
  78 becomes more tricky and users more confused.
  79
  80 I see your point, and yes, an ID alias would be nice, but my personal
  81 feeling is that aliases are not a good thing (tm) :). If you really want the
  82 ID alias - make a wrapper for the IDENTIFY function.
  83
  84 Andrew
  85
  86
  87
  88 </PRE>
  89
  90 <!--endarticle-->
  91     <HR>
  92     <P><UL>
  93         <!--threads-->
  94         <LI>Previous message: <A HREF="000270.html">[IRCServices Coding] More bugs and suggestions for Version 5.0
  95 </A></li>
  96         <LI>Next message: <A HREF="000272.html">[IRCServices Coding] lists
  97 </A></li>
  98          <LI> <B>Messages sorted by:</B>
  99               <a href="date.html#271">[ date ]</a>
 100               <a href="thread.html#271">[ thread ]</a>
 101               <a href="subject.html#271">[ subject ]</a>
 102               <a href="author.html#271">[ author ]</a>
 103          </LI>
 104        </UL>
 105
 106 </body></html>