software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002949.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=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002947.html">
  11    <LINK REL="Next"  HREF="002952.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Another Feature Suggestion</H1>
  15     <B>Ross Hosman</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Another%20Feature%20Suggestion&In-Reply-To="
  17        TITLE="[IRCServices] Another Feature Suggestion">rosshosman at charter.net
  18        </A><BR>
  19     <I>Fri May 31 14:51:00 PDT 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002947.html">[IRCServices] Another Feature Suggestion
  22 </A></li>
  23         <LI>Next message: <A HREF="002952.html">[IRCServices] Another Feature Suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2949">[ date ]</a>
  27               <a href="thread.html#2949">[ thread ]</a>
  28               <a href="subject.html#2949">[ subject ]</a>
  29               <a href="author.html#2949">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>FloodServ - not only do floodbots flood but so do regular users. I believe
  35 this will help keep people from abusing channels when a channel operator is
  36 not there.
  37
  38 RoutingServ - mosty ircd's will autoconnect disconnected servers but some
  39 won't. I also like the idea of services being able to re-rout servers if the
  40 connection to a hub becomes laggy.
  41
  42 NKill - As guy pointed out I have seen alot of floodbots with similiar nick
  43 patterns.
  44
  45 also another feature would be just to have NAkill like flamezservices.
  46 Auto-Kill every host matching that nick that way you don't have to keep
  47 messing with them.
  48 ----- Original Message -----
  49 From: &quot;Russell Garrett&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">rg at tcslon.com</A>&gt;
  50 To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>&gt;
  51 Sent: Friday, May 31, 2002 4:44 AM
  52 Subject: RE: [IRCServices] Another Feature Suggestion
  53
  54
  55 &gt;<i> &gt;FloodServ: Many networks are starting to use this and I have seen
  56 </I>&gt;<i> only one services package implement this into services.
  57 </I>&gt;<i>
  58 </I>&gt;<i> What does FloodServ do that OperServ session limiting and proxy
  59 </I>&gt;<i> scanning doesn't? IMHO proxy scanning shouldn't be implemented into
  60 </I>&gt;<i> services, use a dedicated package like BOPM. If proxy scanning is
  61 </I>&gt;<i> added into services, all malicious users have to do is knock services
  62 </I>&gt;<i> off, then they can connect all their clonebots up. With BOPM, Unreal
  63 </I>&gt;<i> proxy scanning, or similar, you have a bot on each server, so all
  64 </I>&gt;<i> your eggs aren't in one basket so to speak.
  65 </I>&gt;<i>
  66 </I>&gt;<i> &gt;Nkill: Nickname Kill
  67 </I>&gt;<i> &gt;example: /msg operserv nakill guest*
  68 </I>&gt;<i> &gt;will kill everyone with the nick guest. This would be useful for
  69 </I>&gt;<i> floodbots that use the same nicks.
  70 </I>&gt;<i>
  71 </I>&gt;<i> How many floodbots have you seen with similar nicks? Any decent
  72 </I>&gt;<i> self-respecting floodbot program selects random nicks.
  73 </I>&gt;<i>
  74 </I>&gt;<i> &gt;RoutingServ:
  75 </I>&gt;<i> &gt;This would be used to keep a map of the server routing. Which
  76 </I>&gt;<i> servers connect to which hubs, etc. If a server disconnects from the
  77 </I>&gt;<i> hub
  78 </I>&gt;<i> &gt;RoutingServ will auto-connect them. Also if a server becomes lagged
  79 </I>&gt;<i> to hub x services will connect it to hub y with a 30 sec delay with
  80 </I>&gt;<i> &gt;opers being able to cancel the movement.
  81 </I>&gt;<i>
  82 </I>&gt;<i> That piqued my interest there for a moment, but to be honest any
  83 </I>&gt;<i> decent ircd should be able to do most of this itself. Anything else,
  84 </I>&gt;<i> that's what opers are for. I might consider writing a module for
  85 </I>&gt;<i> Services 5 to do this, but I'd have to be quite bored. More bloat for
  86 </I>&gt;<i> not a huge amount of extra gain.
  87 </I>&gt;<i>
  88 </I>&gt;<i> Russ Garrett
  89 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">russ at garrett.co.uk</A>
  90 </I>&gt;<i> www.faereal.net
  91 </I>&gt;<i>
  92 </I>&gt;<i> ------------------------------------------------------------------
  93 </I>&gt;<i> To unsubscribe or change your subscription options, visit:
  94 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
  95 </I>
  96
  97 </PRE>
  98
  99 <!--endarticle-->
 100     <HR>
 101     <P><UL>
 102         <!--threads-->
 103         <LI>Previous message: <A HREF="002947.html">[IRCServices] Another Feature Suggestion
 104 </A></li>
 105         <LI>Next message: <A HREF="002952.html">[IRCServices] Another Feature Suggestion
 106 </A></li>
 107          <LI> <B>Messages sorted by:</B>
 108               <a href="date.html#2949">[ date ]</a>
 109               <a href="thread.html#2949">[ thread ]</a>
 110               <a href="subject.html#2949">[ subject ]</a>
 111               <a href="author.html#2949">[ author ]</a>
 112          </LI>
 113        </UL>
 114
 115 </body></html>