]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
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=42376B1A.1010204%40comcast.net"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="004902.html"> | |
11 | <LINK REL="Next" HREF="004904.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] ChanServ KICK Command</H1> | |
15 | <B>Andrew Church</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20ChanServ%20KICK%20Command&In-Reply-To=42376B1A.1010204%40comcast.net" | |
17 | TITLE="[IRCServices] ChanServ KICK Command">achurch at achurch.org | |
18 | </A><BR> | |
19 | <I>Wed Mar 16 11:16:28 PST 2005</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="004902.html">[IRCServices] ChanServ KICK Command | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="004904.html">[IRCServices] ChanServ KICK Command | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#4903">[ date ]</a> | |
27 | <a href="thread.html#4903">[ thread ]</a> | |
28 | <a href="subject.html#4903">[ subject ]</a> | |
29 | <a href="author.html#4903">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE> Isn't there already +a for unkickable (which Services does respect)? | |
35 | Or does Unreal override +a with +q? | |
36 | ||
37 | --Andrew Church | |
38 | <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
39 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
40 | ||
41 | ><i> For what it's worth, on my network +q is almost never used, but when it | |
42 | </I>><i>is it's often during tracking down botnets or users that are otherwise | |
43 | </I>><i>abusing the network. In this vein it is useful to make it impossible to | |
44 | </I>><i>get kicked out of a channel where you want to be so you can monitor the | |
45 | </I>><i>situation. To that end, it would be useful to me if ChanServ noticed | |
46 | </I>><i>that +q was set on a user and simply denied the kick. I would think | |
47 | </I>><i>that the OperServ kick function should still ignore +q and proceed with | |
48 | </I>><i>the kick, but I'd be interested to hear what others think of this idea. | |
49 | </I>><i> | |
50 | </I>><i>Comments? | |
51 | </I>><i> | |
52 | </I>><i>Bergee | |
53 | </I>><i> | |
54 | </I>><i>Dionisios K. wrote: | |
55 | </I>>><i> On UnrealIRCD the +q usermode is supported. | |
56 | </I>>><i> If an oper (with privileges for this) have this usermode noone can kick | |
57 | </I>>><i> him. | |
58 | </I>>><i> But if someone use the ChanServ KICK command services will kick the oper | |
59 | </I>>><i> from the channel. | |
60 | </I>>><i> I think ChanServ should check if an oper is +q and if yes dont kick him | |
61 | </I>>><i> at all. | |
62 | </I>><i>------------------------------------------------------------------ | |
63 | </I>><i>To unsubscribe or change your subscription options, visit: | |
64 | </I>><i><A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices</A> | |
65 | </I></PRE> | |
66 | ||
67 | ||
68 | ||
69 | ||
70 | ||
71 | <!--endarticle--> | |
72 | <HR> | |
73 | <P><UL> | |
74 | <!--threads--> | |
75 | <LI>Previous message: <A HREF="004902.html">[IRCServices] ChanServ KICK Command | |
76 | </A></li> | |
77 | <LI>Next message: <A HREF="004904.html">[IRCServices] ChanServ KICK Command | |
78 | </A></li> | |
79 | <LI> <B>Messages sorted by:</B> | |
80 | <a href="date.html#4903">[ date ]</a> | |
81 | <a href="thread.html#4903">[ thread ]</a> | |
82 | <a href="subject.html#4903">[ subject ]</a> | |
83 | <a href="author.html#4903">[ author ]</a> | |
84 | </LI> | |
85 | </UL> | |
86 | ||
87 | </body></html> |