1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices Coding] Forbid option?
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Forbid%20option%3F&In-Reply-To=">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"001600.html">
11 <LINK REL=
"Next" HREF=
"001525.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices Coding] Forbid option?
</H1>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Forbid%20option%3F&In-Reply-To="
17 TITLE=
"[IRCServices Coding] Forbid option?">Ganja51 at lcirc.net
19 <I>Thu Oct
10 18:
27:
12 PDT
2002</I>
21 <LI>Previous message:
<A HREF=
"001600.html">[IRCServices Coding] Forbid option?
23 <LI>Next message:
<A HREF=
"001525.html">[IRCServices Coding] MySQL
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1603">[ date ]
</a>
27 <a href=
"thread.html#1603">[ thread ]
</a>
28 <a href=
"subject.html#1603">[ subject ]
</a>
29 <a href=
"author.html#1603">[ author ]
</a>
34 <PRE>Well services obviously has the ability to determine the difference between
35 a user and an IRCop, so you could make it exclude placing an akill on an
36 IRCop if they were in the channel or were to join it. And to make the
37 command applicable to SAs only is a good idea. This is something I'd really
38 like to see added, and hopefully soon. What do you think Andrew?
42 ----- Original Message -----
43 From:
"derfy
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">derfy at derfy.net
</A>>
44 To:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net
</A>>
45 Sent: Thursday, October
10,
2002 7:
43 PM
46 Subject: Re: [IRCServices Coding] Forbid option?
49 On Thu,
10 Oct
2002 23:
56:
17 +
0300 (EEST), you wrote:
51 ><i>Imagine someone or even you entering accidentally the channel...you'll be
52 </I>><i>akilled.to dangerous i think.
55 </I>><i>On Thu,
10 Oct
2002, Ganja51 wrote:
57 </I>>><i> Going along the same lines as the new QLine Kill option, how about an
59 >><i> for ChanServ's Forbid which would allow you to have users which join a
60 </I>>><i> forbidden channel killed or akilled (akilled preferrably). In the case of
61 </I>>><i> bots, they most often have random nicks but join a specific channel. If
63 >><i> forbid the channel, the bots will still be connected to the servers. An
64 </I>>><i> option to have them akilled when they attempt to join a specific channel
65 </I>>><i> would be very handy. Thanks.
67 </I>>><i> ~Ganja51
68 </I>>><i> irc.lcirc.net
71 The idea has merit, maybe move it to an OperServ command available to
72 SAs? Where when you issue it, it adds a timed(perm?) akill on all
73 clients in the channel. Maybe have some error-checking where it won't
74 comply if an oper'd client is in there?
78 where $a = derfy and $b = derfy.net
79 Visit icezip.irctoo.net -
<A HREF=
"http://www.irctoo.net">http://www.irctoo.net
</A>
81 ------------------------------------------------------------------
82 To unsubscribe or change your subscription options, visit:
83 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
92 <LI>Previous message:
<A HREF=
"001600.html">[IRCServices Coding] Forbid option?
94 <LI>Next message:
<A HREF=
"001525.html">[IRCServices Coding] MySQL
96 <LI> <B>Messages sorted by:
</B>
97 <a href=
"date.html#1603">[ date ]
</a>
98 <a href=
"thread.html#1603">[ thread ]
</a>
99 <a href=
"subject.html#1603">[ subject ]
</a>
100 <a href=
"author.html#1603">[ author ]
</a>