software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001342.html

   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="001353.html">
  11    <LINK REL="Next"  HREF="001345.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>Andrew Church</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">achurch at achurch.org
  18        </A><BR>
  19     <I>Mon Feb  5 06:54:04 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001353.html">[IRCServices] How does it work
  22 </A></li>
  23         <LI>Next message: <A HREF="001345.html">[IRCServices] Ok, I think that I have checked all other areas first.  Why the !@#$ does chanserv keep re-opping and re-voic
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1342">[ date ]</a>
  27               <a href="thread.html#1342">[ thread ]</a>
  28               <a href="subject.html#1342">[ subject ]</a>
  29               <a href="author.html#1342">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i>To clarify, I do not mean when a user joins a channel after they identify
  35 </I>&gt;<i>with nickserv.  I mean after a user has been in channel, if they go
  36 </I>&gt;<i>auto-idle away or have been there without action long enough to declare
  37 </I>&gt;<i>idle.  At that point anyone with operator status in the channel (possibly a
  38 </I>&gt;<i>bot, but usually a human) is supposed to remove their ops and voice.  At
  39 </I>&gt;<i>least as of the last tests I made in a channel I test on, chanserv would
  40 </I>&gt;<i>re-voice and re-op them if they had the sufficent level to gain either of
  41 </I>&gt;<i>those upon entry.  This is of course a feature that need at least an on/off
  42 </I>&gt;<i>switch if not removal.  It is not desired in all the cases I can think of
  43 </I>&gt;<i>off hand.
  44 </I>
  45      Meaning your one channel?  When I first implemented this feature most
  46 people appreciated it.  Is there a general opinion on whether this behavior
  47 should change?  Incidentally, I have never heard of this &quot;supposed to remove
  48 their ops and voice&quot; business; don't assume your channel policies apply to
  49 everyone else.
  50
  51 &gt;&gt;<i>      Secure-ops is to disallow users not in the access list from getting
  52 </I>&gt;&gt;<i> ops, not to limit who can set ops on whom.  The HELP text describes this
  53 </I>&gt;&gt;<i> clearly.
  54 </I>&gt;<i>
  55 </I>&gt;<i>Again, to clarify.  If secure-ops is set, chanserv will not allow anyone
  56 </I>&gt;<i>with a level lower then (and equal to?  I forget this point, and can't seem
  57 </I>&gt;<i>to get an answer with &quot;/msg chanserv help levels set autodeop&quot;) auto-deop to
  58 </I>&gt;<i>keep ops.
  59 </I>
  60      *BZZZT* RTFM and try again.
  61
  62 -&gt; *ChanServ* help set secureops
  63 -ChanServ- Syntax: SET channel SECUREOPS {ON | OFF}
  64 -ChanServ-
  65 -ChanServ- Enables or disables the secure ops option for a channel.
  66 -ChanServ- When secure ops is set, users who are not on the userlist
  67 -ChanServ- will not be allowed chanop status.
  68
  69 Incidentally, the command you are looking for is &quot;help levels desc&quot;.
  70
  71 &gt;<i>Thus there should not be a need for chanserv to re-op someone that is
  72 </I>&gt;<i>deopped because anyone with enough access to keep ops is trusted to this
  73 </I>&gt;<i>degree by the founder.
  74 </I>
  75      Does anyone else have an opinion on this?
  76
  77   --Andrew Church
  78     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | New address - please note.
  79     <A HREF="http://achurch.org/">http://achurch.org/</A> | \e$B%a!&lt;%k%&quot;%I%l%9$,JQ$o$j$^$7$?!#\e(B
  80
  81
  82 </PRE>
  83
  84 <!--endarticle-->
  85     <HR>
  86     <P><UL>
  87         <!--threads-->
  88         <LI>Previous message: <A HREF="001353.html">[IRCServices] How does it work
  89 </A></li>
  90         <LI>Next message: <A HREF="001345.html">[IRCServices] Ok, I think that I have checked all other areas first.  Why the !@#$ does chanserv keep re-opping and re-voic
  91 </A></li>
  92          <LI> <B>Messages sorted by:</B>
  93               <a href="date.html#1342">[ date ]</a>
  94               <a href="thread.html#1342">[ thread ]</a>
  95               <a href="subject.html#1342">[ subject ]</a>
  96               <a href="author.html#1342">[ author ]</a>
  97          </LI>
  98        </UL>
  99
 100 </body></html>