software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002952.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Another Feature Suggestion
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Another%20Feature%20Suggestion&In-Reply-To=001e01c208a1%24bfede130%2468c1cf18%40c1065415b">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002949.html">
  11    <LINK REL="Next"  HREF="002953.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Another Feature Suggestion</H1>
  15     <B>Russell Garrett</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Another%20Feature%20Suggestion&In-Reply-To=001e01c208a1%24bfede130%2468c1cf18%40c1065415b"
  17        TITLE="[IRCServices] Another Feature Suggestion">rg at tcslon.com
  18        </A><BR>
  19     <I>Fri May 31 18:13:01 PDT 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002949.html">[IRCServices] Another Feature Suggestion
  22 </A></li>
  23         <LI>Next message: <A HREF="002953.html">[IRCServices] Another Feature Suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2952">[ date ]</a>
  27               <a href="thread.html#2952">[ thread ]</a>
  28               <a href="subject.html#2952">[ subject ]</a>
  29               <a href="author.html#2952">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> FloodServ - not only do floodbots flood but so do regular
  35 </I>&gt;<i> users. I believe
  36 </I>&gt;<i> this will help keep people from abusing channels when a
  37 </I>&gt;<i> channel operator is
  38 </I>&gt;<i> not there.
  39 </I>
  40 OK I see where you're coming from now, but this is requiring Services
  41 to process every single line from every single channel, a not
  42 insignificant load, and probably unreasonable for nets greater than
  43 about 500 to 1000 users. Most (I'm tempted to say all ;) decent ircds
  44 have flood protection built in. It's much more efficient to check it
  45 at the ircd end than at the services end. It's also fallible - if
  46 services is split, you've lost all protection.
  47
  48 &gt;<i> RoutingServ - mosty ircd's will autoconnect disconnected
  49 </I>&gt;<i> servers but some
  50 </I>&gt;<i> won't. I also like the idea of services being able to
  51 </I>&gt;<i> re-rout servers if the
  52 </I>&gt;<i> connection to a hub becomes laggy.
  53 </I>
  54 Also an advantage for smaller nets where you don't have a global oper
  55 on hand all the time I suppose. I'm slowly warming to the idea :).
  56
  57 Russ Garrett
  58 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">russ at garrett.co.uk</A>
  59 www.faereal.net
  60
  61
  62 </PRE>
  63
  64 <!--endarticle-->
  65     <HR>
  66     <P><UL>
  67         <!--threads-->
  68         <LI>Previous message: <A HREF="002949.html">[IRCServices] Another Feature Suggestion
  69 </A></li>
  70         <LI>Next message: <A HREF="002953.html">[IRCServices] Another Feature Suggestion
  71 </A></li>
  72          <LI> <B>Messages sorted by:</B>
  73               <a href="date.html#2952">[ date ]</a>
  74               <a href="thread.html#2952">[ thread ]</a>
  75               <a href="subject.html#2952">[ subject ]</a>
  76               <a href="author.html#2952">[ author ]</a>
  77          </LI>
  78        </UL>
  79
  80 </body></html>