]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002944.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 002944.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=004f01c20886%243cbd6440%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="002943.html">
11 <LINK REL="Next" HREF="002945.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=004f01c20886%243cbd6440%2468c1cf18%40c1065415b"
17 TITLE="[IRCServices] Another Feature Suggestion">rg at tcslon.com
18 </A><BR>
19 <I>Fri May 31 11:45:01 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002943.html">[IRCServices] Another Feature Suggestion
22 </A></li>
23 <LI>Next message: <A HREF="002945.html">Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2944">[ date ]</a>
27 <a href="thread.html#2944">[ thread ]</a>
28 <a href="subject.html#2944">[ subject ]</a>
29 <a href="author.html#2944">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i>FloodServ: Many networks are starting to use this and I have seen
35 </I>only one services package implement this into services.
36
37 What does FloodServ do that OperServ session limiting and proxy
38 scanning doesn't? IMHO proxy scanning shouldn't be implemented into
39 services, use a dedicated package like BOPM. If proxy scanning is
40 added into services, all malicious users have to do is knock services
41 off, then they can connect all their clonebots up. With BOPM, Unreal
42 proxy scanning, or similar, you have a bot on each server, so all
43 your eggs aren't in one basket so to speak.
44
45 &gt;<i>Nkill: Nickname Kill
46 </I>&gt;<i>example: /msg operserv nakill guest*
47 </I>&gt;<i>will kill everyone with the nick guest. This would be useful for
48 </I>floodbots that use the same nicks.
49
50 How many floodbots have you seen with similar nicks? Any decent
51 self-respecting floodbot program selects random nicks.
52
53 &gt;<i>RoutingServ:
54 </I>&gt;<i>This would be used to keep a map of the server routing. Which
55 </I>servers connect to which hubs, etc. If a server disconnects from the
56 hub
57 &gt;<i>RoutingServ will auto-connect them. Also if a server becomes lagged
58 </I>to hub x services will connect it to hub y with a 30 sec delay with
59 &gt;<i>opers being able to cancel the movement.
60 </I>
61 That piqued my interest there for a moment, but to be honest any
62 decent ircd should be able to do most of this itself. Anything else,
63 that's what opers are for. I might consider writing a module for
64 Services 5 to do this, but I'd have to be quite bored. More bloat for
65 not a huge amount of extra gain.
66
67 Russ Garrett
68 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">russ at garrett.co.uk</A>
69 www.faereal.net
70
71
72 </PRE>
73
74 <!--endarticle-->
75 <HR>
76 <P><UL>
77 <!--threads-->
78 <LI>Previous message: <A HREF="002943.html">[IRCServices] Another Feature Suggestion
79 </A></li>
80 <LI>Next message: <A HREF="002945.html">Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)
81 </A></li>
82 <LI> <B>Messages sorted by:</B>
83 <a href="date.html#2944">[ date ]</a>
84 <a href="thread.html#2944">[ thread ]</a>
85 <a href="subject.html#2944">[ subject ]</a>
86 <a href="author.html#2944">[ author ]</a>
87 </LI>
88 </UL>
89
90 </body></html>