[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001348.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices] Ok, I think that I have checked all other areas first.  Why the !@#$ does chanserv keep re-opping and re-voic
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Ok%2C%20I%20think%20that%20I%20have%20checked%20all%20other%20areas%20first.%20%20Why%20the%20%21%40%23%24%20does%20chanserv%20keep%20re-opping%20and%20re-voic&In-Reply-To=">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001343.html">
   <LINK REL="Next"  HREF="001347.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices] Ok, I think that I have checked all other areas first.  Why the !@#$ does chanserv keep re-opping and re-voic</H1>
    <B>Countersync of AGNPH (and #agnph)</B> 
    <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Ok%2C%20I%20think%20that%20I%20have%20checked%20all%20other%20areas%20first.%20%20Why%20the%20%21%40%23%24%20does%20chanserv%20keep%20re-opping%20and%20re-voic&In-Reply-To="
       TITLE="[IRCServices] Ok, I think that I have checked all other areas first.  Why the !@#$ does chanserv keep re-opping and re-voic">countersync at hotmail.com
       </A><BR>
    <I>Sun Feb  4 22:54:05 PST 2001</I>
    <P><UL>
        <LI>Previous message: <A HREF="001343.html">[IRCServices] Ok, I think that I have checked all other areas first.  Why the !@#$ does chanserv keep re-opping and re-voic
</A></li>
        <LI>Next message: <A HREF="001347.html">[IRCServices] Services 4.5pre2 released
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1348">[ date ]</a>
              <a href="thread.html#1348">[ thread ]</a>
              <a href="subject.html#1348">[ subject ]</a>
              <a href="author.html#1348">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>From: &quot;Andrew Church&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>&gt;
To: &quot;Countersync of AGNPH (and #agnph)&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>&gt;
Sent: Sunday, February 04, 2001 13:54
Subject: Re: [IRCServices] Ok, I think that I have checked all other areas
first. Why the !@#$ does chanserv keep re-opping and re-voic


&gt;<i> &gt;To clarify, I do not mean when a user joins a channel after they identify
</I>&gt;<i> &gt;with nickserv.  I mean after a user has been in channel, if they go
</I>&gt;<i> &gt;auto-idle away or have been there without action long enough to declare
</I>&gt;<i> &gt;idle.  At that point anyone with operator status in the channel (possibly
</I>a
&gt;<i> &gt;bot, but usually a human) is supposed to remove their ops and voice.  At
</I>&gt;<i> &gt;least as of the last tests I made in a channel I test on, chanserv would
</I>&gt;<i> &gt;re-voice and re-op them if they had the sufficent level to gain either of
</I>&gt;<i> &gt;those upon entry.  This is of course a feature that need at least an
</I>on/off
&gt;<i> &gt;switch if not removal.  It is not desired in all the cases I can think of
</I>&gt;<i> &gt;off hand.
</I>&gt;<i>
</I>&gt;<i>      Meaning your one channel?  When I first implemented this feature most
</I>&gt;<i> people appreciated it.  Is there a general opinion on whether this
</I>behavior
&gt;<i> should change?  Incidentally, I have never heard of this &quot;supposed to
</I>remove
&gt;<i> their ops and voice&quot; business; don't assume your channel policies apply to
</I>&gt;<i> everyone else.
</I>
Correct, in all of the channels I visit, which isn't many.  Also I didn't
assume they applied to everyone else, just that at some time everyone else
was likely to want to do that same task for one reason or another.
&gt;<i>
</I>&gt;<i> &gt;&gt;      Secure-ops is to disallow users not in the access list from
</I>getting
&gt;<i> &gt;&gt; ops, not to limit who can set ops on whom.  The HELP text describes
</I>this
&gt;<i> &gt;&gt; clearly.
</I>&gt;<i> &gt;
</I>&gt;<i> &gt;Again, to clarify.  If secure-ops is set, chanserv will not allow anyone
</I>&gt;<i> &gt;with a level lower then (and equal to?  I forget this point, and can't
</I>seem
&gt;<i> &gt;to get an answer with &quot;/msg chanserv help levels set autodeop&quot;) auto-deop
</I>to
&gt;<i> &gt;keep ops.
</I>&gt;<i>
</I>&lt;Snip chanserv return for /msg chanserv help set secureops&gt;
&gt;<i> Incidentally, the command you are looking for is &quot;help levels desc&quot;.
</I>
Thanks, this helps, but I still can't see any indication as to the &gt;, &lt;, &lt;=,
or &gt;= function it uses to filter who the levels apply to.
&gt;<i>
</I>&gt;<i> &gt;Thus there should not be a need for chanserv to re-op someone that is
</I>&gt;<i> &gt;deopped because anyone with enough access to keep ops is trusted to this
</I>&gt;<i> &gt;degree by the founder.
</I>&gt;<i>      Does anyone else have an opinion on this?
</I>&gt;<i>   --Andrew Church
</I>&gt;<i>     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | New address - please note.
</I>&gt;<i>     <A HREF="http://achurch.org/">http://achurch.org/</A> | \e$B%a!&lt;%k%&quot;%I%l%9$,JQ$o$j$^$7$?!#\e(B
</I>


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001343.html">[IRCServices] Ok, I think that I have checked all other areas first.  Why the !@#$ does chanserv keep re-opping and re-voic
</A></li>
	<LI>Next message: <A HREF="001347.html">[IRCServices] Services 4.5pre2 released
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1348">[ date ]</a>
              <a href="thread.html#1348">[ thread ]</a>
              <a href="subject.html#1348">[ subject ]</a>
              <a href="author.html#1348">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices] Ok, I think that I have checked all other areas first. Why the !@#$ does chanserv keep re-opping and re-voic
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Ok%2C%20I%20think%20that%20I%20have%20checked%20all%20other%20areas%20first.%20%20Why%20the%20%21%40%23%24%20does%20chanserv%20keep%20re-opping%20and%20re-voic&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="001343.html">
	11	<LINK REL="Next" HREF="001347.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices] Ok, I think that I have checked all other areas first. Why the !@#$ does chanserv keep re-opping and re-voic</H1>
	15	<B>Countersync of AGNPH (and #agnph)</B>
	16	<A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Ok%2C%20I%20think%20that%20I%20have%20checked%20all%20other%20areas%20first.%20%20Why%20the%20%21%40%23%24%20does%20chanserv%20keep%20re-opping%20and%20re-voic&In-Reply-To="
	17	TITLE="[IRCServices] Ok, I think that I have checked all other areas first. Why the !@#$ does chanserv keep re-opping and re-voic">countersync at hotmail.com
	18	</A><BR>
	19	<I>Sun Feb 4 22:54:05 PST 2001</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="001343.html">[IRCServices] Ok, I think that I have checked all other areas first. Why the !@#$ does chanserv keep re-opping and re-voic
	22	</A></li>
	23	<LI>Next message: <A HREF="001347.html">[IRCServices] Services 4.5pre2 released
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#1348">[ date ]</a>
	27	<a href="thread.html#1348">[ thread ]</a>
	28	<a href="subject.html#1348">[ subject ]</a>
	29	<a href="author.html#1348">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>From: "Andrew Church" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>>
	35	To: "Countersync of AGNPH (and #agnph)" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>>
	36	Sent: Sunday, February 04, 2001 13:54
	37	Subject: Re: [IRCServices] Ok, I think that I have checked all other areas
	38	first. Why the !@#$ does chanserv keep re-opping and re-voic
	39
	40
	41	><i> >To clarify, I do not mean when a user joins a channel after they identify
	42	</I>><i> >with nickserv. I mean after a user has been in channel, if they go
	43	</I>><i> >auto-idle away or have been there without action long enough to declare
	44	</I>><i> >idle. At that point anyone with operator status in the channel (possibly
	45	</I>a
	46	><i> >bot, but usually a human) is supposed to remove their ops and voice. At
	47	</I>><i> >least as of the last tests I made in a channel I test on, chanserv would
	48	</I>><i> >re-voice and re-op them if they had the sufficent level to gain either of
	49	</I>><i> >those upon entry. This is of course a feature that need at least an
	50	</I>on/off
	51	><i> >switch if not removal. It is not desired in all the cases I can think of
	52	</I>><i> >off hand.
	53	</I>><i>
	54	</I>><i> Meaning your one channel? When I first implemented this feature most
	55	</I>><i> people appreciated it. Is there a general opinion on whether this
	56	</I>behavior
	57	><i> should change? Incidentally, I have never heard of this "supposed to
	58	</I>remove
	59	><i> their ops and voice" business; don't assume your channel policies apply to
	60	</I>><i> everyone else.
	61	</I>
	62	Correct, in all of the channels I visit, which isn't many. Also I didn't
	63	assume they applied to everyone else, just that at some time everyone else
	64	was likely to want to do that same task for one reason or another.
65	><i>
66	</I>><i> >> Secure-ops is to disallow users not in the access list from
67	</I>getting
68	><i> >> ops, not to limit who can set ops on whom. The HELP text describes
69	</I>this
70	><i> >> clearly.
71	</I>><i> >
72	</I>><i> >Again, to clarify. If secure-ops is set, chanserv will not allow anyone
73	</I>><i> >with a level lower then (and equal to? I forget this point, and can't
74	</I>seem
75	><i> >to get an answer with "/msg chanserv help levels set autodeop") auto-deop
76	</I>to
77	><i> >keep ops.
78	</I>><i>
79	</I><Snip chanserv return for /msg chanserv help set secureops>
80	><i> Incidentally, the command you are looking for is "help levels desc".
81	</I>
82	Thanks, this helps, but I still can't see any indication as to the >, <, <=,
83	or >= function it uses to filter who the levels apply to.
84	><i>
85	</I>><i> >Thus there should not be a need for chanserv to re-op someone that is
86	</I>><i> >deopped because anyone with enough access to keep ops is trusted to this
87	</I>><i> >degree by the founder.
88	</I>><i> Does anyone else have an opinion on this?
89	</I>><i> --Andrew Church
90	</I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> \| New address - please note.
91	</I>><i> <A HREF="http://achurch.org/">http://achurch.org/</A> \| \e$B%a!<%k%"%I%l%9$,JQ$o$j$^$7$?!#\e(B
92	</I>
93
94
95	</PRE>
96
97	<!--endarticle-->
98	<HR>
99	<P><UL>
100	<!--threads-->
101	<LI>Previous message: <A HREF="001343.html">[IRCServices] Ok, I think that I have checked all other areas first. Why the !@#$ does chanserv keep re-opping and re-voic
102	</A></li>
103	<LI>Next message: <A HREF="001347.html">[IRCServices] Services 4.5pre2 released
104	</A></li>
105	<LI> <B>Messages sorted by:</B>
106	<a href="date.html#1348">[ date ]</a>
107	<a href="thread.html#1348">[ thread ]</a>
108	<a href="subject.html#1348">[ subject ]</a>
109	<a href="author.html#1348">[ author ]</a>
110	</LI>
111	</UL>
112
113	</body></html>