]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] IRC Services 5.1 Features | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20IRC%20Services%20%205.1%20Features&In-Reply-To=40f4bea8.70265%40achurch.org"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="004500.html"> | |
11 | <LINK REL="Next" HREF="004509.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] IRC Services 5.1 Features</H1> | |
15 | <B>Bergee</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20IRC%20Services%20%205.1%20Features&In-Reply-To=40f4bea8.70265%40achurch.org" | |
17 | TITLE="[IRCServices] IRC Services 5.1 Features">lordbergee at comcast.net | |
18 | </A><BR> | |
19 | <I>Tue Jul 13 23:11:26 PDT 2004</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="004500.html">[IRCServices] IRC Services 5.1 Features | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="004509.html">[IRCServices] MemoServ Info Display Bug | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#4501">[ date ]</a> | |
27 | <a href="thread.html#4501">[ thread ]</a> | |
28 | <a href="subject.html#4501">[ subject ]</a> | |
29 | <a href="author.html#4501">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Andrew Church wrote: | |
35 | > As far as I understand it (correct me if I'm wrong), channel owner | |
36 | > mode is just like protected (+a) except that it can't be unset by | |
37 | > other +a users; if that's the case, I'm not sure there's much reason | |
38 | > to use it at all--after all, ChanServ will always let the founder | |
39 | > unban, rejoin, and get +a back as needed. | |
40 | > What would people think of just doing away with channel owner | |
41 | > mode support entirely? | |
42 | ||
43 | At least on Unreal that is not quite true. The mode +q (which is used | |
44 | to indicated owner on Unreal) allows you to set or remove channel modes | |
45 | +u (auditorium mode) and +L (channel linking). It also allows you to | |
46 | set/remove +a or +q from users on the channel (and services doesn't | |
47 | enforce +q on anyone, regardless of whether one is the founder). And of | |
48 | course, there's the stuff related to kicking, as a user with +q, you can | |
49 | kick any +a or +q users from the channel, and can't be kicked yourself | |
50 | unless the user trying also has +q. Last but not least, if this feature | |
51 | is enabled, +q also grants the user a different prefix, which a lot of | |
52 | users like to indicate at a glance who runs the channel. | |
53 | On Unreal, given that having it is the only way one can set two channel | |
54 | modes without using services, I think it's a good idea to keep the | |
55 | support for it in place. I would also make the suggestion that if | |
56 | ChanServ enforce is on, that the channel owner mode be enforced if | |
57 | another user removes it. :) | |
58 | ||
59 | Bergee | |
60 | ||
61 | ||
62 | </PRE> | |
63 | ||
64 | <!--endarticle--> | |
65 | <HR> | |
66 | <P><UL> | |
67 | <!--threads--> | |
68 | <LI>Previous message: <A HREF="004500.html">[IRCServices] IRC Services 5.1 Features | |
69 | </A></li> | |
70 | <LI>Next message: <A HREF="004509.html">[IRCServices] MemoServ Info Display Bug | |
71 | </A></li> | |
72 | <LI> <B>Messages sorted by:</B> | |
73 | <a href="date.html#4501">[ date ]</a> | |
74 | <a href="thread.html#4501">[ thread ]</a> | |
75 | <a href="subject.html#4501">[ subject ]</a> | |
76 | <a href="author.html#4501">[ author ]</a> | |
77 | </LI> | |
78 | </UL> | |
79 | ||
80 | </body></html> |