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=">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"000749.html">
11 <LINK REL=
"Next" HREF=
"000751.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Suspended Channels
</H1>
15 <B>Ciar
án Reilly
</B>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suspended%20Channels&In-Reply-To="
17 TITLE=
"[IRCServices] Suspended Channels">Ciaran.reilly at ntlworld.com
19 <I>Sun Sep
17 15:
17:
44 PDT
2000</I>
21 <LI>Previous message:
<A HREF=
"000749.html">[IRCServices] Suspended Channels
23 <LI>Next message:
<A HREF=
"000751.html">[IRCServices] Suspended Channels
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#750">[ date ]
</a>
27 <a href=
"thread.html#750">[ thread ]
</a>
28 <a href=
"subject.html#750">[ subject ]
</a>
29 <a href=
"author.html#750">[ author ]
</a>
34 <PRE>Soz for my rich text post, I'd forget the Newsreader was set to reply to
35 posts using the format in which they were sent :)
37 As for suspension again...... the one drawback with forbid is that the
38 channel is permanently unusable. At the minute, when a user violates net
39 policy and you want to suspend their room, forbid is the only option, and is
40 kind of a rough way of doing it since the only way of reversing it is to
41 drop the chan, not always appropriate. Theres a definate need for a suspend
42 option, and for it to have different levels and be seperate from Forbid.
44 My proposals for the suspend 'levels' would be something similar...
46 Lev
1. Users may join the Channel, users on the Access list may op up etc,
47 BUT the channel database will be in a sort of 'read-only' state, meaning no
48 changes can be made to access / akick lists etc, the topic and modes will be
49 locked, ChanServ will ignore all commands except op deop and identify. This
50 would be useful for a channel you want preserved in it's current state
51 without interfearence from anyone, for whatever reason. Would it be possible
52 to allow Channel founders access to this suspend level ? therefore allowing
53 them to 'freeze' their room and not allow people on the access lists to make
54 any changes ? or is this too much of a stupid idea / security nightmare ?
56 Lev
2. Users may join the Channel, but no one may get ops etc, not even
57 those on the access list or the channel founder, ChanServ will ignore all
58 commands and again the topic and modes will be locked.
60 Lev
3. Channel totally locked out, no users at all may join the channel,
61 just like forbid, only this is easily reversible without the need to drop
64 Thats just my suggestions.....
66 BTW, will SA's and S Root still be able to make changes to channel databases
67 while the suspend mode is in place, thus over riding it, or will they be
68 required to first remove the suspend THEN make the required changes ?
71 Hope some of this is helpful.
79 ----- Original Message -----
80 From:
"Andrew Kempe
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">andrewk at icon.co.za
</A>>
81 To:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org
</A>>
82 Sent: Sunday, September
17,
2000 8:
50 PM
83 Subject: RE: [IRCServices] Suspended Channels
86 ><i> First off, please don't mail this list with HTML/Rich Text emails - only
90 </I>><i> Secondly, FORBID drops the channel prior to rendering useless. This means
91 </I>><i> that all the channel information is lost. It is not the best solution to
92 </I>><i> temporary channel closures.
94 </I>><i> I see the following
3 main states:
95 </I>><i> 1. To be able to freeze a channel's settings but still allow people to
97 ><i> it. Users are not granted any access based on the access lists - all users
98 </I>><i> are deop'ed upon joining. AKICKS and mode locks are enforced.
99 </I>><i> 2. Allow the channel to function as per usual, but no changes may be made
101 ><i> its settings or access/akick lists.
102 </I>><i> 3. Put the channel into a FORBIDen state except that it does not loose its
103 </I>><i> information.
105 </I>><i> Your comments and reasoning are still welcome :)
107 </I>><i> I'll be finishing this off next weekend. Hopefully I'll have worked out
109 ><i> to implement this best by them - flags or levels - so as to suite
114 </I>><i> -----Original Message-----
115 </I>><i> From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at Snow.shadowfire.org
</A>
116 </I>><i> [mailto:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at Snow.shadowfire.org
</A>]On Behalf Of Dr. K. Hawkes
117 </I>><i> Sent:
17 September
2000 18:
28
118 </I>><i> To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org
</A>
119 </I>><i> Subject: Re: [IRCServices] Suspended Channels
122 </I>><i> Freezing the chan is all well and good, but in that case, why the use for
123 </I>><i> the FORBID command?
124 </I>><i> May as well make FORBID and SUSPEND as one command unless you make the new
125 </I>><i> FORBID command with levels, which you could integrate SUSPEND
130 </I>><i> ----------
131 </I>><i> > From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">dreamer at darkness.gr
</A>
132 </I>><i> > To: IRCServices
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org
</A>>
133 </I>><i> > Subject: Re: [IRCServices] Suspended Channels
134 </I>><i> > Date: Sunday, September
17,
2000 16:
34
136 </I>><i> > Greetings all,
138 </I>><i> > I had the same idea before months. I believe that the best idea
139 </I>><i> > based on
"channel suspension
" is to
"Freeze
" the channel.
141 </I>><i> > That could be :
142 </I>><i> > Not allowing the users to join the channel,
143 </I>><i> > Preserve the access list of the channel, plus any akicks and levels
144 </I>><i> > settings.
145 </I>><i> > And for sure , never allowing a change in the access list of that
148 </I>><i> > If possible , an enforce could be implement, that will kick all users
150 ><i> > of channel by the time of suspension. And also, a non strict suspend,
152 ><i> > could let users to join the channel but totally freeze the levels and
153 </I>><i> > access lists could be an idea.
155 </I>><i> > Regards,
156 </I>><i> > Nick Krassas
159 </I>><i> > On Sun,
17 Sep
2000, Andrew Kempe wrote:
161 </I>><i> > > I'm finishing off the implementation of channel suspensions. I was
162 </I>><i> wondering
163 </I>><i> > > what the general feeling was regarding the effect a suspension has on
165 ><i> > > channel.
166 </I>><i> > >
167 </I>><i> > > Should a suspended channel:
168 </I>><i> > > - allow users to join?
169 </I>><i> > > - operate normally but prevent any setting or access-list changes from
171 </I>><i> > > made?
172 </I>><i> > > - prevent changes from being made and not grant access as per the
173 </I>><i> channel's
174 </I>><i> > > access list?
175 </I>><i> > >
176 </I>><i> > > Would various levels of suspension be usefull? Would this be too
177 </I>><i> confusing?
178 </I>><i> > > Should this be a level-based or flag-based system?
179 </I>><i> > >
180 </I>><i> > > Your ideas would be appreciated.
181 </I>><i> > >
182 </I>><i> > > Thanks, Andrew
185 </I>><i> > ---------------------------------------------------------------
186 </I>><i> > To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
187 </I>><i> > with
"unsubscribe ircservices
" in the body, without the quotes.
190 </I>><i> ---------------------------------------------------------------
191 </I>><i> To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
192 </I>><i> with
"unsubscribe ircservices
" in the body, without the quotes.
195 ---------------------------------------------------------------
196 To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
197 with
"unsubscribe ircservices
" in the body, without the quotes.
206 <LI>Previous message:
<A HREF=
"000749.html">[IRCServices] Suspended Channels
208 <LI>Next message:
<A HREF=
"000751.html">[IRCServices] Suspended Channels
210 <LI> <B>Messages sorted by:
</B>
211 <a href=
"date.html#750">[ date ]
</a>
212 <a href=
"thread.html#750">[ thread ]
</a>
213 <a href=
"subject.html#750">[ subject ]
</a>
214 <a href=
"author.html#750">[ author ]
</a>
projects / irc.git / blob