1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] Feature Requests (CS: FREEZE and an INFO field)
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=mpcflucj6l2bm0hafdap3hq7bc1od920tj%404ax.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=
"003053.html">
11 <LINK REL=
"Next" HREF=
"003055.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Feature Requests (CS: FREEZE and an INFO field)
</H1>
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=mpcflucj6l2bm0hafdap3hq7bc1od920tj%404ax.com"
17 TITLE=
"[IRCServices] Feature Requests (CS: FREEZE and an INFO field)">bundy at usage.de
19 <I>Mon Aug
12 16:
57:
00 PDT
2002</I>
21 <LI>Previous message:
<A HREF=
"003053.html">[IRCServices] Feature Requests (CS: FREEZE and an INFO field)
23 <LI>Next message:
<A HREF=
"003055.html">[IRCServices] Feature Requests (CS: FREEZE and an INFO field)
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#3054">[ date ]
</a>
27 <a href=
"thread.html#3054">[ thread ]
</a>
28 <a href=
"subject.html#3054">[ subject ]
</a>
29 <a href=
"author.html#3054">[ author ]
</a>
34 <PRE>On
2002-
08-
12 (
08:
37, -
0500), derfy
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">derfy at derfy.net
</A>> wrote:
36 ><i> I apologize if this has been brought up before; I did a search on
37 </I>><i> 'suspend', 'freeze'(these turned up promising, but I didn't see any
38 </I>><i> yes/no/maybe/RTFM/STFU/etc), and anything else I could think of.
40 </I>><i> Currently, ChanServ has two 'punishment' settings: Suspend and Forbid.
41 </I>><i> I would like to suggest a 'freeze' option. Features follow:
43 </I>><i> - It would have an optional time(IE: /chanserv freeze #chan
<expiry
>
44 </I>><i> <reason
>)
45 </I>><i> - It would make the channel effectively unregistered in regard to the
46 </I>><i> access list(except akicks); mlocks, topics would remain
49 </I>><i> Also, another suggestion. Establish an Info field, perhaps
255 chars,
50 </I>><i> visible only to opers(plain +o clients) that Services admins(opers?)
51 </I>><i> can put in a description of problems with the channel. Example:
53 </I>><i> - /chanserv set #chan operinfo Do *not* getpass/sendpass this channel
54 </I>><i> without talking to me first!
55 </I>><i> would result in:
57 </I>><i> (
08:
32:
59 am) -ChanServ- Information for channel #chan:
58 </I>><i> (
08:
32:
59 am) -ChanServ- OperInfo: Do *not* getpass/sendpass this
59 </I>><i> channel without talking to me first! (derfy,
08/
12/
2002 0830 -
0600<too
60 </I>><i> much?
>)
63 Sounds like you want a bunch of DALnet features.
65 First of all Chanserv has a great
"suspend
" function including
"expire
"
66 and
"reason
" fields. I don't see a benefit in a (dal-services like)
67 "freeze
" option. However, I like the second suggestion to tag chans with
68 informations only available for opers. I'd like to see that in ircservices
74 *** Scharping has quit (Connection reset by Schroeder)
83 <LI>Previous message:
<A HREF=
"003053.html">[IRCServices] Feature Requests (CS: FREEZE and an INFO field)
85 <LI>Next message:
<A HREF=
"003055.html">[IRCServices] Feature Requests (CS: FREEZE and an INFO field)
87 <LI> <B>Messages sorted by:
</B>
88 <a href=
"date.html#3054">[ date ]
</a>
89 <a href=
"thread.html#3054">[ thread ]
</a>
90 <a href=
"subject.html#3054">[ subject ]
</a>
91 <a href=
"author.html#3054">[ author ]
</a>