1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices Coding]
5.0.36 and Unreal
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=20040726142343.GD30439%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=
"003070.html">
11 <LINK REL=
"Next" HREF=
"003072.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices Coding]
5.0.36 and Unreal
</H1>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%205.0.36%20and%20Unreal&In-Reply-To=20040726142343.GD30439%40phat.za.net"
17 TITLE=
"[IRCServices Coding] 5.0.36 and Unreal">martinpels at hotmail.com
19 <I>Mon Jul
26 07:
49:
21 PDT
2004</I>
21 <LI>Previous message:
<A HREF=
"003070.html">[IRCServices Coding]
5.0.36 and Unreal
23 <LI>Next message:
<A HREF=
"003072.html">[IRCServices Coding]
5.0.36 and Unreal
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#3071">[ date ]
</a>
27 <a href=
"thread.html#3071">[ thread ]
</a>
28 <a href=
"subject.html#3071">[ subject ]
</a>
29 <a href=
"author.html#3071">[ author ]
</a>
34 <PRE>><i> I suspect I'm the only one with this opinion.
36 Nope, I completely agree :-)
38 The mode +q is given to channel owners only, and because of this it
39 should not be possible for users with accesslevel
100 (channel admin) to
40 remove this mode (if they can this makes +q useless, because after
41 removing +q through Services a channel admin will be able to kick the
42 owner). So PROTECT/DEPROTECT should only add or remove +a.
44 On Mon,
2004-
07-
26 at
16:
23, Aragon Gouveia wrote:
45 ><i> | By Andrew Church
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A>>
46 </I>><i> | [
2004-
07-
26 15:
31 +
0200 ]
47 </I>><i> > Actually, what would be best from my perspective is if someone--or
48 </I>><i> > even better, several someones--made their own hacks to Services on their
49 </I>><i> > own network to do what they thought was the
"right thing
", and some sort of
50 </I>><i> > consensus arose from there. (I often look to Services derivatives for
51 </I>><i> > ideas as well; is anyone aware of a Services-like program that does use the
52 </I>><i> > channel owner mode, and if so, how does it use the mode?)
54 </I>><i> I don't know of anything apart from the IRCd itself.
57 </I>><i> > I think a lot of the problem is that chanowner and protected (+a)
58 </I>><i> > overlap too much--there isn't anything a chanowner can _do_ other than not
59 </I>><i> > get de-ownered(?) by +a users, and maybe set a couple of modes that could
60 </I>><i> > be just as easily handled by SET MLOCK. At the moment it's just an
61 </I>><i> > extraneous, unnecessary privilege level, and I think that's what's causing
62 </I>><i> > a lot of the confusion.
64 </I>><i> Yea, that's right.
66 </I>><i> Current Unreal protocol dictates that
67 </I>><i> channel owners (+q) can:
68 </I>><i> Set the channel +u
69 </I>><i> Set the channel +L
70 </I>><i> Set a channel user +a
71 </I>><i> Set a channel user +q
72 </I>><i> Set all other channel modes normal chanops can set
73 </I>><i> Kick anyone in the channel
74 </I>><i> NOT be kicked by anyone but another owner
75 </I>><i> NOT be deopped by anyone but another owner
76 </I>><i> NOT be de-q'd by anyone but another owner
77 </I>><i> NOT be de-a'd by anyone but another owner
79 </I>><i> channel admins (+a) can:
80 </I>><i> Set the same channel modes normal chanops can set
81 </I>><i> NOT be kicked by anyone but an owner
82 </I>><i> NOT be deopped by anyone but an owner
83 </I>><i> NOT be de-a'd by anyone but an owner
84 </I>><i> NOT kick other channel admins
85 </I>><i> NOT deop other channel admins
86 </I>><i> NOT de-a other channel admins
89 </I>><i> The confusion for me is this:
91 </I>><i> -ChanServ- PROTECT Give a user protected status (+a)
92 </I>><i> -ChanServ- DEPROTECT Remove protected status (+a)
94 </I>><i> The (DE)PROTECT commands are labelled as being capable of adding/removing
95 </I>><i> +a status. However, the DEPROTECT command will remove +a and +q.
96 </I>><i> Additionally, channel admin status is essentially just a chanop status
97 </I>><i> providing kick/deop protection. Channel ownership is more than that, which
98 </I>><i> is why I think DEPROTECT should not have the ability of removing that
99 </I>><i> status. IMHO that control should be reserved for the ChanServ
100 </I>><i> FOUNDER, SUCCESSOR, and holder(s) of the founder password.
102 </I>><i> I suspect I'm the only one with this opinion. In which case, no worries..
103 </I>><i> will mod the source. I originally posted thinking it'd be a simple bug
104 </I>><i> report. :)
110 </I>><i> ------------------------------------------------------------------
111 </I>><i> To unsubscribe or change your subscription options, visit:
112 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
122 <LI>Previous message:
<A HREF=
"003070.html">[IRCServices Coding]
5.0.36 and Unreal
124 <LI>Next message:
<A HREF=
"003072.html">[IRCServices Coding]
5.0.36 and Unreal
126 <LI> <B>Messages sorted by:
</B>
127 <a href=
"date.html#3071">[ date ]
</a>
128 <a href=
"thread.html#3071">[ thread ]
</a>
129 <a href=
"subject.html#3071">[ subject ]
</a>
130 <a href=
"author.html#3071">[ author ]
</a>
projects / irc.git / blob