]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000745.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2000 / 000745.html
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="000742.html">
11 <LINK REL="Next" HREF="000747.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Suspended Channels</H1>
15 <B>Ciar&#225;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
18 </A><BR>
19 <I>Sun Sep 17 07:31:32 PDT 2000</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000742.html">[IRCServices] Suspended Channels
22 </A></li>
23 <LI>Next message: <A HREF="000747.html">[IRCServices] Suspended Channels
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#745">[ date ]</a>
27 <a href="thread.html#745">[ thread ]</a>
28 <a href="subject.html#745">[ subject ]</a>
29 <a href="author.html#745">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>
35 I'd agree, I think levels of suspension would be useful. As someone mentioned, Forbid stops a channel being used at all, so it would be good to have an 'in-between' function which allowe dthe channel to be joined but it would be useless as far as using Services and changing settings was concerned. So yeah, suspend should have varying levels of suspension...... Just my $0.02
36
37 BTW, is the Services Ignore function likely to be implemented in a forthcoming release ? I think it's something that'd be really useful....I don't think i'm confident enough with the code yet to try and get it working myself either...
38
39 Cheers,
40
41 Ciar&#225;n
42
43
44 ----- Original Message -----
45 From: Dr. K. Hawkes
46 To: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ender.shadowfire.org</A>
47 Sent: Sunday, September 17, 2000 3:03 PM
48 Subject: Re: [IRCServices] Suspended Channels
49
50
51
52 Well, as FORBID totally disallows a channel from being used or registered, you'd ideally want something inbetween standard operation and FORBID.
53
54 &gt;<i> Should a suspended channel:
55 </I>&gt;<i> - allow users to join?
56 </I>IMHO - Yes, FORBID stops users joining.
57
58 &gt;<i> - operate normally but prevent any setting or access-list changes from being
59 </I>&gt;<i> made?
60 </I>This would be a good thing to have, allows flexibility.
61
62 &gt;<i> - prevent changes from being made and not grant access as per the channel's
63 </I>&gt;<i> access list?
64 </I>I'm not too sure on this one, prevent changes from being made is a good one again, but if you go to all this trouble of suspending a chan, why not simply FORBID it?
65
66 &gt;<i>
67 </I>&gt;<i> Would various levels of suspension be usefull? Would this be too confusing?
68 </I>Now that would be a nice idea :c)
69
70 &gt;<i> Should this be a level-based or flag-based system?
71 </I>Personally, I'd go for level-based...
72
73 E.g. Lev 1 - Chan Operates as normal except users on access list
74 which are given +o normally only get +v (or something) ...
75 Then go Lev 4 - Users can join chan, but access list is ignored, no settings can be changed etc...
76
77 Just my thoughts on it :c)
78
79 Quinn
80 ----------
81 &gt;<i> From: Andrew Kempe &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">andrewk at icon.co.za</A>&gt;
82 </I>&gt;<i> To: IRCServices &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at delirious.shadowfire.org</A>&gt;
83 </I>&gt;<i> Subject: [IRCServices] Suspended Channels
84 </I>&gt;<i> Date: Sunday, September 17, 2000 14:40
85 </I>&gt;<i>
86 </I>&gt;<i> I'm finishing off the implementation of channel suspensions. I was wondering
87 </I>&gt;<i> what the general feeling was regarding the effect a suspension has on a
88 </I>&gt;<i> channel.
89 </I>&gt;<i>
90 </I>&gt;<i> Should a suspended channel:
91 </I>&gt;<i> - allow users to join?
92 </I>&gt;<i> - operate normally but prevent any setting or access-list changes from being
93 </I>&gt;<i> made?
94 </I>&gt;<i> - prevent changes from being made and not grant access as per the channel's
95 </I>&gt;<i> access list?
96 </I>&gt;<i>
97 </I>&gt;<i> Would various levels of suspension be usefull? Would this be too confusing?
98 </I>&gt;<i> Should this be a level-based or flag-based system?
99 </I>&gt;<i>
100 </I>&gt;<i> Your ideas would be appreciated.
101 </I>&gt;<i>
102 </I>&gt;<i> Thanks, Andrew
103 </I>&gt;<i>
104 </I>&gt;<i>
105 </I>&gt;<i> ---------------------------------------------------------------
106 </I>&gt;<i> To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
107 </I>&gt;<i> with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
108 </I></PRE>
109
110 <!--endarticle-->
111 <HR>
112 <P><UL>
113 <!--threads-->
114 <LI>Previous message: <A HREF="000742.html">[IRCServices] Suspended Channels
115 </A></li>
116 <LI>Next message: <A HREF="000747.html">[IRCServices] Suspended Channels
117 </A></li>
118 <LI> <B>Messages sorted by:</B>
119 <a href="date.html#745">[ date ]</a>
120 <a href="thread.html#745">[ thread ]</a>
121 <a href="subject.html#745">[ subject ]</a>
122 <a href="author.html#745">[ author ]</a>
123 </LI>
124 </UL>
125
126 </body></html>