]> jfr.im git - irc.git/blobdiff - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002949.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 002949.html
diff --git a/software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002949.html b/software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002949.html
new file mode 100644 (file)
index 0000000..577d562
--- /dev/null
@@ -0,0 +1,115 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+   <TITLE> [IRCServices] Another Feature Suggestion
+   </TITLE>
+   <LINK REL="Index" HREF="index.html" >
+   <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Another%20Feature%20Suggestion&In-Reply-To=">
+   <META NAME="robots" CONTENT="index,nofollow">
+   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+   <LINK REL="Previous"  HREF="002947.html">
+   <LINK REL="Next"  HREF="002952.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+   <H1>[IRCServices] Another Feature Suggestion</H1>
+    <B>Ross Hosman</B> 
+    <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Another%20Feature%20Suggestion&In-Reply-To="
+       TITLE="[IRCServices] Another Feature Suggestion">rosshosman at charter.net
+       </A><BR>
+    <I>Fri May 31 14:51:00 PDT 2002</I>
+    <P><UL>
+        <LI>Previous message: <A HREF="002947.html">[IRCServices] Another Feature Suggestion
+</A></li>
+        <LI>Next message: <A HREF="002952.html">[IRCServices] Another Feature Suggestion
+</A></li>
+         <LI> <B>Messages sorted by:</B> 
+              <a href="date.html#2949">[ date ]</a>
+              <a href="thread.html#2949">[ thread ]</a>
+              <a href="subject.html#2949">[ subject ]</a>
+              <a href="author.html#2949">[ author ]</a>
+         </LI>
+       </UL>
+    <HR>  
+<!--beginarticle-->
+<PRE>FloodServ - not only do floodbots flood but so do regular users. I believe
+this will help keep people from abusing channels when a channel operator is
+not there.
+
+RoutingServ - mosty ircd's will autoconnect disconnected servers but some
+won't. I also like the idea of services being able to re-rout servers if the
+connection to a hub becomes laggy.
+
+NKill - As guy pointed out I have seen alot of floodbots with similiar nick
+patterns.
+
+also another feature would be just to have NAkill like flamezservices.
+Auto-Kill every host matching that nick that way you don't have to keep
+messing with them.
+----- Original Message -----
+From: &quot;Russell Garrett&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">rg at tcslon.com</A>&gt;
+To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>&gt;
+Sent: Friday, May 31, 2002 4:44 AM
+Subject: RE: [IRCServices] Another Feature Suggestion
+
+
+&gt;<i> &gt;FloodServ: Many networks are starting to use this and I have seen
+</I>&gt;<i> only one services package implement this into services.
+</I>&gt;<i>
+</I>&gt;<i> What does FloodServ do that OperServ session limiting and proxy
+</I>&gt;<i> scanning doesn't? IMHO proxy scanning shouldn't be implemented into
+</I>&gt;<i> services, use a dedicated package like BOPM. If proxy scanning is
+</I>&gt;<i> added into services, all malicious users have to do is knock services
+</I>&gt;<i> off, then they can connect all their clonebots up. With BOPM, Unreal
+</I>&gt;<i> proxy scanning, or similar, you have a bot on each server, so all
+</I>&gt;<i> your eggs aren't in one basket so to speak.
+</I>&gt;<i>
+</I>&gt;<i> &gt;Nkill: Nickname Kill
+</I>&gt;<i> &gt;example: /msg operserv nakill guest*
+</I>&gt;<i> &gt;will kill everyone with the nick guest. This would be useful for
+</I>&gt;<i> floodbots that use the same nicks.
+</I>&gt;<i>
+</I>&gt;<i> How many floodbots have you seen with similar nicks? Any decent
+</I>&gt;<i> self-respecting floodbot program selects random nicks.
+</I>&gt;<i>
+</I>&gt;<i> &gt;RoutingServ:
+</I>&gt;<i> &gt;This would be used to keep a map of the server routing. Which
+</I>&gt;<i> servers connect to which hubs, etc. If a server disconnects from the
+</I>&gt;<i> hub
+</I>&gt;<i> &gt;RoutingServ will auto-connect them. Also if a server becomes lagged
+</I>&gt;<i> to hub x services will connect it to hub y with a 30 sec delay with
+</I>&gt;<i> &gt;opers being able to cancel the movement.
+</I>&gt;<i>
+</I>&gt;<i> That piqued my interest there for a moment, but to be honest any
+</I>&gt;<i> decent ircd should be able to do most of this itself. Anything else,
+</I>&gt;<i> that's what opers are for. I might consider writing a module for
+</I>&gt;<i> Services 5 to do this, but I'd have to be quite bored. More bloat for
+</I>&gt;<i> not a huge amount of extra gain.
+</I>&gt;<i>
+</I>&gt;<i> Russ Garrett
+</I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">russ at garrett.co.uk</A>
+</I>&gt;<i> www.faereal.net
+</I>&gt;<i>
+</I>&gt;<i> ------------------------------------------------------------------
+</I>&gt;<i> To unsubscribe or change your subscription options, visit:
+</I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
+</I>
+
+</PRE>
+
+<!--endarticle-->
+    <HR>
+    <P><UL>
+        <!--threads-->
+       <LI>Previous message: <A HREF="002947.html">[IRCServices] Another Feature Suggestion
+</A></li>
+       <LI>Next message: <A HREF="002952.html">[IRCServices] Another Feature Suggestion
+</A></li>
+         <LI> <B>Messages sorted by:</B> 
+              <a href="date.html#2949">[ date ]</a>
+              <a href="thread.html#2949">[ thread ]</a>
+              <a href="subject.html#2949">[ subject ]</a>
+              <a href="author.html#2949">[ author ]</a>
+         </LI>
+       </UL>
+
+</body></html>