RELEASE -> !RELEASE

[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2005 / 004902.html
diff --git a/software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2005/004902.html b/software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2005/004902.html

new file mode 100644 (file)

index 0000000..8620fa6
--- /dev/null
+++ b/software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2005/004902.html
@@ -0,0 +1,77 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+   <TITLE> [IRCServices] ChanServ KICK Command
+   </TITLE>
+   <LINK REL="Index" HREF="index.html" >
+   <LINK REL="made" HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20ChanServ%20KICK%20Command&In-Reply-To=000301c526b4%24c1217010%24484405d5%40server">
+   <META NAME="robots" CONTENT="index,nofollow">
+   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+   <LINK REL="Previous"  HREF="004899.html">
+   <LINK REL="Next"  HREF="004903.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+   <H1>[IRCServices] ChanServ KICK Command</H1>
+    <B>Bergee</B> 
+    <A HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20ChanServ%20KICK%20Command&In-Reply-To=000301c526b4%24c1217010%24484405d5%40server"
+       TITLE="[IRCServices] ChanServ KICK Command">lordbergee at comcast.net
+       </A><BR>
+    <I>Tue Mar 15 15:09:14 PST 2005</I>
+    <P><UL>
+        <LI>Previous message: <A HREF="004899.html">[IRCServices] ChanServ KICK Command
+</A></li>
+        <LI>Next message: <A HREF="004903.html">[IRCServices] ChanServ KICK Command
+</A></li>
+         <LI> <B>Messages sorted by:</B> 
+              <a href="date.html#4902">[ date ]</a>
+              <a href="thread.html#4902">[ thread ]</a>
+              <a href="subject.html#4902">[ subject ]</a>
+              <a href="author.html#4902">[ author ]</a>
+         </LI>
+       </UL>
+    <HR>  
+<!--beginarticle-->
+<PRE>  For what it's worth, on my network +q is almost never used, but when it 
+is it's often during tracking down botnets or users that are otherwise 
+abusing the network.  In this vein it is useful to make it impossible to 
+get kicked out of a channel where you want to be so you can monitor the 
+situation.  To that end, it would be useful to me if ChanServ noticed 
+that +q was set on a user and simply denied the kick.  I would think 
+that the OperServ kick function should still ignore +q and proceed with 
+the kick, but I'd be interested to hear what others think of this idea.
+
+Comments?
+
+Bergee
+
+Dionisios K. wrote:
+&gt;<i> On UnrealIRCD the +q usermode is supported.
+</I>&gt;<i> If an oper (with privileges for this) have this usermode noone can kick 
+</I>&gt;<i> him.
+</I>&gt;<i> But if someone use the ChanServ KICK command services will kick the oper 
+</I>&gt;<i> from the channel.
+</I>&gt;<i> I think ChanServ should check if an oper is +q and if yes dont kick him 
+</I>&gt;<i> at all.
+</I></PRE>
+
+
+
+
+
+<!--endarticle-->
+    <HR>
+    <P><UL>
+        <!--threads-->
+       <LI>Previous message: <A HREF="004899.html">[IRCServices] ChanServ KICK Command
+</A></li>
+       <LI>Next message: <A HREF="004903.html">[IRCServices] ChanServ KICK Command
+</A></li>
+         <LI> <B>Messages sorted by:</B> 
+              <a href="date.html#4902">[ date ]</a>
+              <a href="thread.html#4902">[ thread ]</a>
+              <a href="subject.html#4902">[ subject ]</a>
+              <a href="author.html#4902">[ author ]</a>
+         </LI>
+       </UL>
+
+</body></html>