]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2005/004908.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2005 / 004908.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=3143.69.175.9.85.1110940196.squirrel%40webmail.wwwpages.com">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="004907.html">
11 <LINK REL="Next" HREF="004910.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] ChanServ KICK Command</H1>
15 <B>Rottman3D at yahoo.com</B>
16 <A HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20ChanServ%20KICK%20Command&In-Reply-To=3143.69.175.9.85.1110940196.squirrel%40webmail.wwwpages.com"
17 TITLE="[IRCServices] ChanServ KICK Command">Rottman3D at yahoo.com
18 </A><BR>
19 <I>Tue Mar 15 18:34:05 PST 2005</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="004907.html">[IRCServices] ChanServ KICK Command
22 </A></li>
23 <LI>Next message: <A HREF="004910.html">[IRCServices] ChanServ KICK Command
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#4908">[ date ]</a>
27 <a href="thread.html#4908">[ thread ]</a>
28 <a href="subject.html#4908">[ subject ]</a>
29 <a href="author.html#4908">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Yes, U-lined servers should have the ability to kick +q users but they
35 should not allow users the power to remove opers. Opers are there to handle
36 unruly users, as such if an oper has the ability to protect himself from
37 kicks, in my opinion, services should respect that.
38
39 -R
40
41
42 At 09:29 PM 3/15/2005, you wrote:
43 &gt;<i>pardon my pointing out the obvious, but services is a U: line, therefore
44 </I>&gt;<i>according to the unreal help, chanserv should be able to kick a +q user.
45 </I>&gt;<i>
46 </I>&gt;<i>
47 </I>&gt;<i>
48 </I>&gt;<i>On Tue, March 15, 2005 6:25 pm, Bergee said:
49 </I>&gt;<i> &gt; Sorry I should have been more clear the first time. :) I was
50 </I>&gt;<i> speaking
51 </I>&gt;<i> &gt; about the user mode +q, not the channel mode. The unreal help describes
52 </I>&gt;<i> &gt; this mode as &quot;q = Only U:lines can kick you (Services Admins/Net Admins
53 </I>&gt;<i> &gt; only)&quot;. Although the part about service/net admins only isn't quite
54 </I>&gt;<i> &gt; true since it could in theory be any oper with the access to that mode
55 </I>&gt;<i> &gt; defined in their oper block. But I digress, hopefully that makes my
56 </I>&gt;<i> &gt; last post make a bit more sense.
57 </I>&gt;<i> &gt;
58 </I>&gt;<i> &gt; Bergee
59 </I>&gt;<i> &gt;
60 </I>&gt;<i> &gt; P.S. Speaking of the +a and +q channel modes, Unreal now (with prefixes
61 </I>&gt;<i> &gt; for +a and +q enabled) treats the channel modes +a and +q more like +h
62 </I>&gt;<i> &gt; than just a status marker for not kickable. Except of course they have
63 </I>&gt;<i> &gt; more power than +o instead of less. As in if you have +a or +q, you
64 </I>&gt;<i> &gt; don't actually need +o to kick a user from the channel, or to give
65 </I>&gt;<i> &gt; another user halfops and so on like that. But I suppose that's another
66 </I>&gt;<i> &gt; email. :)
67 </I>&gt;<i> &gt;
68 </I>&gt;<i> &gt; Andrew Church wrote:
69 </I>&gt;<i> &gt;
70 </I>&gt;<i> &gt;&gt; Isn't there already +a for unkickable (which Services does
71 </I>&gt;<i> &gt;&gt; respect)?
72 </I>&gt;<i> &gt;&gt; Or does Unreal override +a with +q?
73 </I>&gt;<i> &gt;&gt;
74 </I>&gt;<i> &gt;&gt; --Andrew Church
75 </I>&gt;<i> &gt;&gt; <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
76 </I>&gt;<i> &gt;&gt;
77 </I>&gt;<i> &gt;&gt;
78 </I>&gt;<i> &gt;&gt;
79 </I>&gt;<i> &gt;&gt;&gt; For what it's worth, on my network +q is almost never used, but
80 </I>&gt;<i> when it
81 </I>&gt;<i> &gt;&gt;&gt;is it's often during tracking down botnets or users that are otherwise
82 </I>&gt;<i> &gt;&gt;&gt;abusing the network. In this vein it is useful to make it impossible to
83 </I>&gt;<i> &gt;&gt;&gt;get kicked out of a channel where you want to be so you can monitor the
84 </I>&gt;<i> &gt;&gt;&gt;situation. To that end, it would be useful to me if ChanServ noticed
85 </I>&gt;<i> &gt;&gt;&gt;that +q was set on a user and simply denied the kick. I would think
86 </I>&gt;<i> &gt;&gt;&gt;that the OperServ kick function should still ignore +q and proceed with
87 </I>&gt;<i> &gt;&gt;&gt;the kick, but I'd be interested to hear what others think of this idea.
88 </I>&gt;<i> &gt;&gt;&gt;
89 </I>&gt;<i> &gt;&gt;&gt;Comments?
90 </I>&gt;<i> &gt;&gt;&gt;
91 </I>&gt;<i> &gt;&gt;&gt;Bergee
92 </I>&gt;<i> &gt;&gt;&gt;
93 </I>&gt;<i> &gt;&gt;&gt;Dionisios K. wrote:
94 </I>&gt;<i> &gt;&gt;&gt;
95 </I>&gt;<i> &gt;&gt;&gt;&gt;On UnrealIRCD the +q usermode is supported.
96 </I>&gt;<i> &gt;&gt;&gt;&gt;If an oper (with privileges for this) have this usermode noone can kick
97 </I>&gt;<i> &gt;&gt;&gt;&gt;him.
98 </I>&gt;<i> &gt;&gt;&gt;&gt;But if someone use the ChanServ KICK command services will kick the
99 </I>&gt;<i> &gt;&gt;&gt;&gt; oper
100 </I>&gt;<i> &gt;&gt;&gt;&gt;from the channel.
101 </I>&gt;<i> &gt;&gt;&gt;&gt;I think ChanServ should check if an oper is +q and if yes dont kick him
102 </I>&gt;<i> &gt;&gt;&gt;&gt;at all.
103 </I>&gt;<i> &gt;&gt;&gt;
104 </I>
105
106 </PRE>
107
108
109
110
111
112 <!--endarticle-->
113 <HR>
114 <P><UL>
115 <!--threads-->
116 <LI>Previous message: <A HREF="004907.html">[IRCServices] ChanServ KICK Command
117 </A></li>
118 <LI>Next message: <A HREF="004910.html">[IRCServices] ChanServ KICK Command
119 </A></li>
120 <LI> <B>Messages sorted by:</B>
121 <a href="date.html#4908">[ date ]</a>
122 <a href="thread.html#4908">[ thread ]</a>
123 <a href="subject.html#4908">[ subject ]</a>
124 <a href="author.html#4908">[ author ]</a>
125 </LI>
126 </UL>
127
128 </body></html>