1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] ChanServ does not add NickServ noop to ChanServ
7 <LINK REL=
"Index" HREF=
"index.html" >
8 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20does%20not%20add%20NickServ%20noop%20to%20ChanServ%0A%09NeverOp&In-Reply-To=d50f59a00709140433v7cb2ce07t2a933e1a530cc3c1%40mail.gmail.com">
9 <META NAME=
"robots" CONTENT=
"index,nofollow">
10 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
11 <LINK REL=
"Previous" HREF=
"005446.html">
12 <LINK REL=
"Next" HREF=
"005444.html">
14 <BODY BGCOLOR=
"#ffffff">
15 <H1>[IRCServices] ChanServ does not add NickServ noop to ChanServ
18 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20does%20not%20add%20NickServ%20noop%20to%20ChanServ%0A%09NeverOp&In-Reply-To=d50f59a00709140433v7cb2ce07t2a933e1a530cc3c1%40mail.gmail.com"
19 TITLE=
"[IRCServices] ChanServ does not add NickServ noop to ChanServ
20 NeverOp">achurch at achurch.org
22 <I>Sat Sep
29 07:
59:
30 PDT
2007</I>
24 <LI>Previous message:
<A HREF=
"005446.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
27 <LI>Next message:
<A HREF=
"005444.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
30 <LI> <B>Messages sorted by:
</B>
31 <a href=
"date.html#5461">[ date ]
</a>
32 <a href=
"thread.html#5461">[ thread ]
</a>
33 <a href=
"subject.html#5461">[ subject ]
</a>
34 <a href=
"author.html#5461">[ author ]
</a>
39 <PRE>To be honest, I don't see much purpose in a feature like NOOP either, but
40 enough people have asked for it that there must be some use for it I'm not
44 <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A>
45 <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
47 ><i>--===============
1655919240==
48 </I>><i>Content-Type: multipart/alternative;
49 </I>><i> boundary=
"----=_Part_2043_16579049.1189769630972
"
51 </I>><i>------=_Part_2043_16579049.1189769630972
52 </I>><i>Content-Type: text/plain; charset=ISO-
8859-
1
53 </I>><i>Content-Transfer-Encoding:
7bit
54 </I>><i>Content-Disposition: inline
56 </I>><i>i think this feature is too blurry at the moment,
57 </I>><i>here's my proposal:
58 </I>><i>nickserv/noacm (no automatic channel mode) [add del list clear] [#channel]
59 </I>><i>everything's snappy, only user doesn't get auto ops/halfops/voices
60 </I>><i>regardless of channel auto levels.
61 </I>><i>there's a decision to be made for the channel parameter, it can be the
62 </I>><i>channels id number in the db, that way, when someone drops the channel, it
63 </I>><i>gets deleted from this list and the setting is
"reset
", or, we can use
64 </I>><i>wildcards and have the setting stick to a channel even after owners change.
65 </I>><i>also you can have a second option (instead of #channel), for example
"ALL
",
66 </I>><i>or wildcard #* to have this option enabled globaly.
67 </I>><i>i'm in favor of the wildcard idea but it might be a performance issue.
68 </I>><i>i see no real purpose to have a user setting
"don't op me ever
", just don't
69 </I>><i>be in a channel and stuff, but not having it automatic might have a good
71 </I>><i>i'll also run a pole with our users to see what they think.
73 </I>><i>best regards
76 </I>><i>------=_Part_2043_16579049.1189769630972
77 </I>><i>Content-Type: text/html; charset=ISO-
8859-
1
78 </I>><i>Content-Transfer-Encoding:
7bit
79 </I>><i>Content-Disposition: inline
81 </I>><i>i think this feature is too blurry at the moment,
<br
>here
&#
39;s my proposal:
<br
>nickserv/noacm (no automatic channel mode) [add del list clear] [#channel]
<br
>everything
&#
39;s snappy, only user doesn
&#
39;t get auto ops/halfops/voices regardless of channel
82 </I>><i>auto levels.
83 </I>><i><br
>there
&#
39;s a decision to be made for the channel parameter, it can be the channels id number in the db, that way, when someone drops the channel, it gets deleted from this list and the setting is
&quot;reset
&quot;, or, we can use wildcards and have t
84 </I>><i>he setting stick to a channel even after owners change.
85 </I>><i><br
>also you can have a second option (instead of #channel), for example
&quot;ALL
&quot;, or wildcard #* to have this option enabled globaly.
<br
>i
&#
39;m in favor of the wildcard idea but it might be a performance issue.
<br
>
86 </I>><i>i see no real purpose to have a user setting
&quot;don
&#
39;t op me ever
&quot;, just don
&#
39;t be in a channel and stuff, but not having it automatic might have a good purpose.
<br
>i
&#
39;ll also run a pole with our users to see what they think.
87 </I>><i><br
><br
>best regards
<br
>PHANTOm
<br
>
89 </I>><i>------=_Part_2043_16579049.1189769630972--
91 </I>><i>--===============
1655919240==
92 </I>><i>Content-Type: text/plain; charset=
"us-ascii
"
93 </I>><i>MIME-Version:
1.0
94 </I>><i>Content-Transfer-Encoding:
7bit
95 </I>><i>Content-Disposition: inline
97 </I>><i>------------------------------------------------------------------
98 </I>><i>To unsubscribe or change your subscription options, visit:
105 <LI>Previous message:
<A HREF=
"005446.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
108 <LI>Next message:
<A HREF=
"005444.html">[IRCServices] ChanServ does not add NickServ noop to ChanServ
111 <LI> <B>Messages sorted by:
</B>
112 <a href=
"date.html#5461">[ date ]
</a>
113 <a href=
"thread.html#5461">[ thread ]
</a>
114 <a href=
"subject.html#5461">[ subject ]
</a>
115 <a href=
"author.html#5461">[ author ]
</a>
projects / irc.git / blob