]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/003052.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 003052.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Feature Requests (CS: FREEZE and an INFO field)
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Feature%20Requests%20%28CS%3A%20FREEZE%20and%20an%20INFO%20field%29&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="003051.html">
11 <LINK REL="Next" HREF="003053.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Feature Requests (CS: FREEZE and an INFO field)</H1>
15 <B>derfy</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Feature%20Requests%20%28CS%3A%20FREEZE%20and%20an%20INFO%20field%29&In-Reply-To="
17 TITLE="[IRCServices] Feature Requests (CS: FREEZE and an INFO field)">derfy at derfy.net
18 </A><BR>
19 <I>Mon Aug 12 15:38:00 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003051.html">[IRCServices] Operserv bug crashes Services
22 </A></li>
23 <LI>Next message: <A HREF="003053.html">[IRCServices] Feature Requests (CS: FREEZE and an INFO field)
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#3052">[ date ]</a>
27 <a href="thread.html#3052">[ thread ]</a>
28 <a href="subject.html#3052">[ subject ]</a>
29 <a href="author.html#3052">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>I apologize if this has been brought up before; I did a search on
35 'suspend', 'freeze'(these turned up promising, but I didn't see any
36 yes/no/maybe/RTFM/STFU/etc), and anything else I could think of.
37
38 Currently, ChanServ has two 'punishment' settings: Suspend and Forbid.
39 I would like to suggest a 'freeze' option. Features follow:
40
41 - It would have an optional time(IE: /chanserv freeze #chan &lt;expiry&gt;
42 &lt;reason&gt;)
43 - It would make the channel effectively unregistered in regard to the
44 access list(except akicks); mlocks, topics would remain
45
46
47 Also, another suggestion. Establish an Info field, perhaps 255 chars,
48 visible only to opers(plain +o clients) that Services admins(opers?)
49 can put in a description of problems with the channel. Example:
50
51 - /chanserv set #chan operinfo Do *not* getpass/sendpass this channel
52 without talking to me first!
53 would result in:
54
55 (08:32:59 am) -ChanServ- Information for channel #chan:
56 (08:32:59 am) -ChanServ- OperInfo: Do *not* getpass/sendpass this
57 channel without talking to me first! (derfy, 08/12/2002 0830 -0600&lt;too
58 much?&gt;)
59 ..etc..
60
61 Just some thoughts.
62 Very nice job on services.
63
64 --
65 $a@$b
66 where $a = derfy and $b = derfy.net
67 Visit icezip.irctoo.net - <A HREF="http://www.irctoo.net">http://www.irctoo.net</A>
68 IRCtoo++;
69
70 </PRE>
71
72 <!--endarticle-->
73 <HR>
74 <P><UL>
75 <!--threads-->
76 <LI>Previous message: <A HREF="003051.html">[IRCServices] Operserv bug crashes Services
77 </A></li>
78 <LI>Next message: <A HREF="003053.html">[IRCServices] Feature Requests (CS: FREEZE and an INFO field)
79 </A></li>
80 <LI> <B>Messages sorted by:</B>
81 <a href="date.html#3052">[ date ]</a>
82 <a href="thread.html#3052">[ thread ]</a>
83 <a href="subject.html#3052">[ subject ]</a>
84 <a href="author.html#3052">[ author ]</a>
85 </LI>
86 </UL>
87
88 </body></html>