]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Suspended Channels | |
5 | </TITLE> | |
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="000745.html"> | |
11 | <LINK REL="Next" HREF="000749.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Suspended Channels</H1> | |
15 | <B>&quot</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suspended%20Channels&In-Reply-To=" | |
17 | TITLE="[IRCServices] Suspended Channels">&quot | |
18 | </A><BR> | |
19 | <I>Sun Sep 17 09:27:30 PDT 2000</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="000745.html">[IRCServices] Suspended Channels | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="000749.html">[IRCServices] Suspended Channels | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#747">[ date ]</a> | |
27 | <a href="thread.html#747">[ thread ]</a> | |
28 | <a href="subject.html#747">[ subject ]</a> | |
29 | <a href="author.html#747">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE> | |
35 | ||
36 | Freezing the chan is all well and good, but in that case, why the use for the FORBID command? | |
37 | May as well make FORBID and SUSPEND as one command unless you make the new FORBID command with levels, which you could integrate SUSPEND functionality into. | |
38 | ||
39 | Quinn | |
40 | ---------- | |
41 | ><i> From: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">dreamer at darkness.gr</A> | |
42 | </I>><i> To: IRCServices <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org</A>> | |
43 | </I>><i> Subject: Re: [IRCServices] Suspended Channels | |
44 | </I>><i> Date: Sunday, September 17, 2000 16:34 | |
45 | </I>><i> | |
46 | </I>><i> Greetings all, | |
47 | </I>><i> | |
48 | </I>><i> &#009;I had the same idea before months. I believe that the best idea | |
49 | </I>><i> based on "channel suspension" is to "Freeze" the channel. | |
50 | </I>><i> | |
51 | </I>><i> That could be : | |
52 | </I>><i> Not allowing the users to join the channel, | |
53 | </I>><i> Preserve the access list of the channel, plus any akicks and levels | |
54 | </I>><i> settings. | |
55 | </I>><i> And for sure , never allowing a change in the access list of that channel. | |
56 | </I>><i> | |
57 | </I>><i> If possible , an enforce could be implement, that will kick all users out | |
58 | </I>><i> of channel by the time of suspension. And also, a non strict suspend, that | |
59 | </I>><i> could let users to join the channel but totally freeze the levels and | |
60 | </I>><i> access lists could be an idea. | |
61 | </I>><i> | |
62 | </I>><i> Regards, | |
63 | </I>><i> Nick Krassas | |
64 | </I>><i> | |
65 | </I>><i> | |
66 | </I>><i> On Sun, 17 Sep 2000, Andrew Kempe wrote: | |
67 | </I>><i> | |
68 | </I>><i> > I'm finishing off the implementation of channel suspensions. I was wondering | |
69 | </I>><i> > what the general feeling was regarding the effect a suspension has on a | |
70 | </I>><i> > channel. | |
71 | </I>><i> > | |
72 | </I>><i> > Should a suspended channel: | |
73 | </I>><i> > - allow users to join? | |
74 | </I>><i> > - operate normally but prevent any setting or access-list changes from being | |
75 | </I>><i> > made? | |
76 | </I>><i> > - prevent changes from being made and not grant access as per the channel's | |
77 | </I>><i> > access list? | |
78 | </I>><i> > | |
79 | </I>><i> > Would various levels of suspension be usefull? Would this be too confusing? | |
80 | </I>><i> > Should this be a level-based or flag-based system? | |
81 | </I>><i> > | |
82 | </I>><i> > Your ideas would be appreciated. | |
83 | </I>><i> > | |
84 | </I>><i> > Thanks, Andrew | |
85 | </I>><i> | |
86 | </I>><i> | |
87 | </I>><i> --------------------------------------------------------------- | |
88 | </I>><i> To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A> | |
89 | </I>><i> with "unsubscribe ircservices" in the body, without the quotes. | |
90 | </I></PRE> | |
91 | ||
92 | <!--endarticle--> | |
93 | <HR> | |
94 | <P><UL> | |
95 | <!--threads--> | |
96 | <LI>Previous message: <A HREF="000745.html">[IRCServices] Suspended Channels | |
97 | </A></li> | |
98 | <LI>Next message: <A HREF="000749.html">[IRCServices] Suspended Channels | |
99 | </A></li> | |
100 | <LI> <B>Messages sorted by:</B> | |
101 | <a href="date.html#747">[ date ]</a> | |
102 | <a href="thread.html#747">[ thread ]</a> | |
103 | <a href="subject.html#747">[ subject ]</a> | |
104 | <a href="author.html#747">[ author ]</a> | |
105 | </LI> | |
106 | </UL> | |
107 | ||
108 | </body></html> |