]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices Coding] 5.0.36 and Unreal | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%205.0.36%20and%20Unreal&In-Reply-To=20040726113807.GA23937%40phat.za.net"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="003068.html"> | |
11 | <LINK REL="Next" HREF="003070.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] 5.0.36 and Unreal</H1> | |
15 | <B>Andrew Church</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%205.0.36%20and%20Unreal&In-Reply-To=20040726113807.GA23937%40phat.za.net" | |
17 | TITLE="[IRCServices Coding] 5.0.36 and Unreal">achurch at achurch.org | |
18 | </A><BR> | |
19 | <I>Mon Jul 26 22:21:57 PDT 2004</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="003068.html">[IRCServices Coding] 5.0.36 and Unreal | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="003070.html">[IRCServices Coding] 5.0.36 and Unreal | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#3069">[ date ]</a> | |
27 | <a href="thread.html#3069">[ thread ]</a> | |
28 | <a href="subject.html#3069">[ subject ]</a> | |
29 | <a href="author.html#3069">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>><i>Hrm, sorry to throw the spanner into the works. What if the Unreal dev team | |
35 | </I>><i>suggested how this should work? | |
36 | </I> | |
37 | Actually, what would be best from my perspective is if someone--or | |
38 | even better, several someones--made their own hacks to Services on their | |
39 | own network to do what they thought was the "right thing", and some sort of | |
40 | consensus arose from there. (I often look to Services derivatives for | |
41 | ideas as well; is anyone aware of a Services-like program that does use the | |
42 | channel owner mode, and if so, how does it use the mode?) | |
43 | ||
44 | I think a lot of the problem is that chanowner and protected (+a) | |
45 | overlap too much--there isn't anything a chanowner can _do_ other than not | |
46 | get de-ownered(?) by +a users, and maybe set a couple of modes that could | |
47 | be just as easily handled by SET MLOCK. At the moment it's just an | |
48 | extraneous, unnecessary privilege level, and I think that's what's causing | |
49 | a lot of the confusion. | |
50 | ||
51 | --Andrew Church | |
52 | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A> | |
53 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
54 | ||
55 | ||
56 | </PRE> | |
57 | ||
58 | <!--endarticle--> | |
59 | <HR> | |
60 | <P><UL> | |
61 | <!--threads--> | |
62 | <LI>Previous message: <A HREF="003068.html">[IRCServices Coding] 5.0.36 and Unreal | |
63 | </A></li> | |
64 | <LI>Next message: <A HREF="003070.html">[IRCServices Coding] 5.0.36 and Unreal | |
65 | </A></li> | |
66 | <LI> <B>Messages sorted by:</B> | |
67 | <a href="date.html#3069">[ date ]</a> | |
68 | <a href="thread.html#3069">[ thread ]</a> | |
69 | <a href="subject.html#3069">[ subject ]</a> | |
70 | <a href="author.html#3069">[ author ]</a> | |
71 | </LI> | |
72 | </UL> | |
73 | ||
74 | </body></html> |