1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] Suspended Channels
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suspended%20Channels&In-Reply-To=E13aiMj-0001f2-00%40praseodumium.btinternet.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=
"000747.html">
11 <LINK REL=
"Next" HREF=
"000750.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Suspended Channels
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suspended%20Channels&In-Reply-To=E13aiMj-0001f2-00%40praseodumium.btinternet.com"
17 TITLE=
"[IRCServices] Suspended Channels">&quot
19 <I>Sun Sep
17 12:
50:
44 PDT
2000</I>
21 <LI>Previous message:
<A HREF=
"000747.html">[IRCServices] Suspended Channels
23 <LI>Next message:
<A HREF=
"000750.html">[IRCServices] Suspended Channels
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#749">[ date ]
</a>
27 <a href=
"thread.html#749">[ thread ]
</a>
28 <a href=
"subject.html#749">[ subject ]
</a>
29 <a href=
"author.html#749">[ author ]
</a>
34 <PRE>First off, please don't mail this list with HTML/Rich Text emails - only use
37 Secondly, FORBID drops the channel prior to rendering useless. This means
38 that all the channel information is lost. It is not the best solution to
39 temporary channel closures.
41 I see the following
3 main states:
42 1. To be able to freeze a channel's settings but still allow people to join
43 it. Users are not granted any access based on the access lists - all users
44 are deop'ed upon joining. AKICKS and mode locks are enforced.
45 2. Allow the channel to function as per usual, but no changes may be made to
46 its settings or access/akick lists.
47 3. Put the channel into a FORBIDen state except that it does not loose its
50 Your comments and reasoning are still welcome :)
52 I'll be finishing this off next weekend. Hopefully I'll have worked out how
53 to implement this best by them - flags or levels - so as to suite everyone.
57 -----Original Message-----
58 From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at Snow.shadowfire.org
</A>
59 [mailto:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at Snow.shadowfire.org
</A>]On Behalf Of Dr. K. Hawkes
60 Sent:
17 September
2000 18:
28
61 To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org
</A>
62 Subject: Re: [IRCServices] Suspended Channels
65 Freezing the chan is all well and good, but in that case, why the use for
67 May as well make FORBID and SUSPEND as one command unless you make the new
68 FORBID command with levels, which you could integrate SUSPEND functionality
73 ><i> From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">dreamer at darkness.gr
</A>
74 </I>><i> To: IRCServices
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org
</A>>
75 </I>><i> Subject: Re: [IRCServices] Suspended Channels
76 </I>><i> Date: Sunday, September
17,
2000 16:
34
78 </I>><i> Greetings all,
80 </I>><i> I had the same idea before months. I believe that the best idea
81 </I>><i> based on
"channel suspension
" is to
"Freeze
" the channel.
83 </I>><i> That could be :
84 </I>><i> Not allowing the users to join the channel,
85 </I>><i> Preserve the access list of the channel, plus any akicks and levels
87 </I>><i> And for sure , never allowing a change in the access list of that channel.
89 </I>><i> If possible , an enforce could be implement, that will kick all users out
90 </I>><i> of channel by the time of suspension. And also, a non strict suspend, that
91 </I>><i> could let users to join the channel but totally freeze the levels and
92 </I>><i> access lists could be an idea.
95 </I>><i> Nick Krassas
98 </I>><i> On Sun,
17 Sep
2000, Andrew Kempe wrote:
100 </I>><i> > I'm finishing off the implementation of channel suspensions. I was
102 ><i> > what the general feeling was regarding the effect a suspension has on a
103 </I>><i> > channel.
105 </I>><i> > Should a suspended channel:
106 </I>><i> > - allow users to join?
107 </I>><i> > - operate normally but prevent any setting or access-list changes from
110 </I>><i> > - prevent changes from being made and not grant access as per the
112 ><i> > access list?
114 </I>><i> > Would various levels of suspension be usefull? Would this be too
116 ><i> > Should this be a level-based or flag-based system?
118 </I>><i> > Your ideas would be appreciated.
120 </I>><i> > Thanks, Andrew
123 </I>><i> ---------------------------------------------------------------
124 </I>><i> To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
125 </I>><i> with
"unsubscribe ircservices
" in the body, without the quotes.
128 ---------------------------------------------------------------
129 To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
130 with
"unsubscribe ircservices
" in the body, without the quotes.
139 <LI>Previous message:
<A HREF=
"000747.html">[IRCServices] Suspended Channels
141 <LI>Next message:
<A HREF=
"000750.html">[IRCServices] Suspended Channels
143 <LI> <B>Messages sorted by:
</B>
144 <a href=
"date.html#749">[ date ]
</a>
145 <a href=
"thread.html#749">[ thread ]
</a>
146 <a href=
"subject.html#749">[ subject ]
</a>
147 <a href=
"author.html#749">[ author ]
</a>
projects / irc.git / blob