]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2006/005141.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2006 / 005141.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] feature info
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20feature%20info&In-Reply-To=HGELJGPKLJIDOHBEAMCBKEPNDAAA.ContactBox%40flashmail.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="005140.html">
11 <LINK REL="Next" HREF="005142.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] feature info</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20feature%20info&In-Reply-To=HGELJGPKLJIDOHBEAMCBKEPNDAAA.ContactBox%40flashmail.com"
17 TITLE="[IRCServices] feature info">achurch at achurch.org
18 </A><BR>
19 <I>Sun Apr 30 22:36:25 PDT 2006</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="005140.html">[IRCServices] feature info
22 </A></li>
23 <LI>Next message: <A HREF="005142.html">[IRCServices] IRC Services channel mode loophole
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#5141">[ date ]</a>
27 <a href="thread.html#5141">[ thread ]</a>
28 <a href="subject.html#5141">[ subject ]</a>
29 <a href="author.html#5141">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i>I'm using Unreal, and the problem is that I want to be able to use
35 </I>&gt;<i>time-specified bans (or akicks), but have chanserv expire them after the
36 </I>&gt;<i>time's up. So that a channel op can set a 2 hour ban, or 3 day ban to deal
37 </I>&gt;<i>with minor disruptive conduct, and the limit will be honored and doesn't
38 </I>&gt;<i>rely on the op remembering to turn the ban off when it expires 3 days later.
39 </I>&gt;<i>What I'd *really* like is an extended AKICK option format:
40 </I>
41 I'll think about this for 5.1, but in the meantime (particularly since
42 I'm busy with other obligations and won't be able to work on Services for a
43 while) you may want to look at the AKILL/SQLINE/etc. ADD command processing
44 in modules/operserv/maskdata.c, which recognizes a &quot;+&lt;time&gt;&quot; initial
45 parameter as an expiration time. You'll also need to modify the autokick
46 structure, obviously; for 5.0, this will break your databases unless you
47 change the database version and add code in modules/database/version4.c to
48 handle the version differences (5.1 takes care of all this automatically).
49 You may want to ask on the coding list for more help.
50
51 &gt;<i>As a further comment on AKICK, it'd be nice (if possible) if it listed bans
52 </I>&gt;<i>by number (like memos are listed), so that one didnt have to retype the mask
53 </I>&gt;<i>but could just replace &lt;mask&gt; by &lt;number&gt; in AKICK commands, if desired.
54 </I>
55 As a rule, I'm trying to stay away from numbered lists where possible.
56 Particularly in the case where the lists can get renumbered after adds or
57 deletions, you can get unexpected behavior:
58
59 (User1 -&gt; ChanServ) AKICK #channel LIST
60 (ChanServ -&gt; User1) Autokick list for #channel:
61 (ChanServ -&gt; User1) 1 *@some.host.com
62 (ChanServ -&gt; User1) 2 *@minor.annoyance.org
63 (ChanServ -&gt; User1) 3 *@deadly.cracker.net
64 [User1 starts typing &quot;AKICK...&quot;, intending to delete *@some.host.com]
65 (User2 -&gt; ChanServ) AKICK #channel LIST
66 (ChanServ -&gt; User2) Autokick list for #channel:
67 (ChanServ -&gt; User2) 1 *@some.host.com
68 (ChanServ -&gt; User2) 2 *@minor.annoyance.org
69 (ChanServ -&gt; User2) 3 *@deadly.cracker.net
70 [User2 starts typing &quot;AKICK...&quot;, intending to delete *@minor.annoyance.org]
71 (User1 -&gt; ChanServ) AKICK #channel DEL 1
72 (ChanServ -&gt; User1) *@some.host.com deleted from #channel autokick list.
73 (User1 -&gt; ChanServ) AKICK #channel LIST
74 (ChanServ -&gt; User1) Autokick list for #channel:
75 (ChanServ -&gt; User1) 1 *@minor.annoyance.org
76 (ChanServ -&gt; User1) 2 *@deadly.cracker.net
77 (User2 -&gt; ChanServ) AKICK #channel DEL 2
78 (ChanServ -&gt; User2) *@deadly.cracker.net deleted from #channel autokick list.
79
80 This can be avoided by attaching unique numbers to each autokick, but
81 then you can get lists like 5, 13, 28... with holes in the sequence, plus
82 you have an extra field that you have to deal with loading and saving. If
83 you made the ID non-numeric, you wouldn't have to worry about the oddity of
84 holes in the sequence--but then why not just use the mask itself as the ID?
85 That saves the trouble of keeping track of an extra field as well.
86
87 That's my reasoning behind not using numbered lists. That, plus it's
88 really not that hard to type the mask in, or even copy and paste, for the
89 comparatively infrequent occasions you need the command...
90
91 --Andrew Church
92 <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
93 <A HREF="http://achurch.org/">http://achurch.org/</A>
94 </PRE>
95
96
97 <!--endarticle-->
98 <HR>
99 <P><UL>
100 <!--threads-->
101 <LI>Previous message: <A HREF="005140.html">[IRCServices] feature info
102 </A></li>
103 <LI>Next message: <A HREF="005142.html">[IRCServices] IRC Services channel mode loophole
104 </A></li>
105 <LI> <B>Messages sorted by:</B>
106 <a href="date.html#5141">[ date ]</a>
107 <a href="thread.html#5141">[ thread ]</a>
108 <a href="subject.html#5141">[ subject ]</a>
109 <a href="author.html#5141">[ author ]</a>
110 </LI>
111 </UL>
112
113 </body></html>