software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2005/004902.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] ChanServ KICK Command
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20ChanServ%20KICK%20Command&In-Reply-To=000301c526b4%24c1217010%24484405d5%40server">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="004899.html">
  11    <LINK REL="Next"  HREF="004903.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] ChanServ KICK Command</H1>
  15     <B>Bergee</B>
  16     <A HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20ChanServ%20KICK%20Command&In-Reply-To=000301c526b4%24c1217010%24484405d5%40server"
  17        TITLE="[IRCServices] ChanServ KICK Command">lordbergee at comcast.net
  18        </A><BR>
  19     <I>Tue Mar 15 15:09:14 PST 2005</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="004899.html">[IRCServices] ChanServ KICK Command
  22 </A></li>
  23         <LI>Next message: <A HREF="004903.html">[IRCServices] ChanServ KICK Command
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#4902">[ date ]</a>
  27               <a href="thread.html#4902">[ thread ]</a>
  28               <a href="subject.html#4902">[ subject ]</a>
  29               <a href="author.html#4902">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>   For what it's worth, on my network +q is almost never used, but when it
  35 is it's often during tracking down botnets or users that are otherwise
  36 abusing the network.  In this vein it is useful to make it impossible to
  37 get kicked out of a channel where you want to be so you can monitor the
  38 situation.  To that end, it would be useful to me if ChanServ noticed
  39 that +q was set on a user and simply denied the kick.  I would think
  40 that the OperServ kick function should still ignore +q and proceed with
  41 the kick, but I'd be interested to hear what others think of this idea.
  42
  43 Comments?
  44
  45 Bergee
  46
  47 Dionisios K. wrote:
  48 &gt;<i> On UnrealIRCD the +q usermode is supported.
  49 </I>&gt;<i> If an oper (with privileges for this) have this usermode noone can kick
  50 </I>&gt;<i> him.
  51 </I>&gt;<i> But if someone use the ChanServ KICK command services will kick the oper
  52 </I>&gt;<i> from the channel.
  53 </I>&gt;<i> I think ChanServ should check if an oper is +q and if yes dont kick him
  54 </I>&gt;<i> at all.
  55 </I></PRE>
  56
  57
  58
  59
  60
  61 <!--endarticle-->
  62     <HR>
  63     <P><UL>
  64         <!--threads-->
  65         <LI>Previous message: <A HREF="004899.html">[IRCServices] ChanServ KICK Command
  66 </A></li>
  67         <LI>Next message: <A HREF="004903.html">[IRCServices] ChanServ KICK Command
  68 </A></li>
  69          <LI> <B>Messages sorted by:</B>
  70               <a href="date.html#4902">[ date ]</a>
  71               <a href="thread.html#4902">[ thread ]</a>
  72               <a href="subject.html#4902">[ subject ]</a>
  73               <a href="author.html#4902">[ author ]</a>
  74          </LI>
  75        </UL>
  76
  77 </body></html>