[IRCServices] Another Feature Suggestion
rg at tcslon.com
Fri May 31 11:45:01 PDT 2002
>FloodServ: Many networks are starting to use this and I have seen
only one services package implement this into services.
What does FloodServ do that OperServ session limiting and proxy
scanning doesn't? IMHO proxy scanning shouldn't be implemented into
services, use a dedicated package like BOPM. If proxy scanning is
added into services, all malicious users have to do is knock services
off, then they can connect all their clonebots up. With BOPM, Unreal
proxy scanning, or similar, you have a bot on each server, so all
your eggs aren't in one basket so to speak.
>Nkill: Nickname Kill
>example: /msg operserv nakill guest*
>will kill everyone with the nick guest. This would be useful for
floodbots that use the same nicks.
How many floodbots have you seen with similar nicks? Any decent
self-respecting floodbot program selects random nicks.
>This would be used to keep a map of the server routing. Which
servers connect to which hubs, etc. If a server disconnects from the
>RoutingServ will auto-connect them. Also if a server becomes lagged
to hub x services will connect it to hub y with a 30 sec delay with
>opers being able to cancel the movement.
That piqued my interest there for a moment, but to be honest any
decent ircd should be able to do most of this itself. Anything else,
that's what opers are for. I might consider writing a module for
Services 5 to do this, but I'd have to be quite bored. More bloat for
not a huge amount of extra gain.
russ at garrett.co.uk