software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000537.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] ACCESS and *OP
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ACCESS%20and%20%2AOP&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="000535.html">
  11    <LINK REL="Next"  HREF="000538.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] ACCESS and *OP</H1>
  15     <B>Kelmar K. Firesun</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ACCESS%20and%20%2AOP&In-Reply-To="
  17        TITLE="[IRCServices] ACCESS and *OP">kfiresun at ix.netcom.com
  18        </A><BR>
  19     <I>Sat May 13 12:58:24 PDT 2000</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000535.html">[IRCServices] ACCESS and *OP
  22 </A></li>
  23         <LI>Next message: <A HREF="000538.html">[IRCServices] 4.4.x ETA
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#537">[ date ]</a>
  27               <a href="thread.html#537">[ thread ]</a>
  28               <a href="subject.html#537">[ subject ]</a>
  29               <a href="author.html#537">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Andy Wrote:
  35
  36 ] ... SNIP ... [
  37
  38 &gt;<i>
  39 </I>&gt;<i>     As for the addition of AOP/SOP/etc commands, I am not overly against
  40 </I>&gt;<i>them except inasmuch as they represent a &quot;standard&quot; that doesn't have to
  41 </I>&gt;<i>be a standard; I also remember quite well the numerous complaints that
  42 </I>&gt;<i>people found the level system difficult to use.  On the other hand, I have
  43 </I>&gt;<i>come to detest the attitude of Microsoft (among others) to do their best
  44 </I>&gt;<i>to keep you ignorant even if you know what you're doing, and taking out
  45 </I>&gt;<i>the ACCESS command would be too close to that for my liking.  What I would
  46 </I>&gt;<i>recommend is to add the *OP functions, either as commands or as
  47 </I>&gt;<i>alternatives for the ACCESS ADD level value, and have those functions in
  48 </I>&gt;<i>turn call ACCESS ADD with an appropriate level.  Naturally, this would not
  49 </I>&gt;<i>work if the channel levels had been changed, but by adding an EXPERT
  50 </I>&gt;<i>channel option as someone else suggested and disallowing level changes
  51 </I>&gt;<i>without EXPERT set, AOP/SOP/etc become workable again under the ACCESS
  52 </I>&gt;<i>system.
  53 </I>&gt;<i>
  54 </I>
  55 I don't see why an AOP/SOP/etc. command couldn't look at the level settings
  56 themselves and use those numbers....  I.E. if a founder of a channel sets
  57 the Auto Oping level to 4, why can't the AOP ADD &lt;NICK&gt; command just add
  58 said
  59 nick at level 4?
  60
  61 &gt;<i>
  62 </I>&gt;<i>     My personal preference is to use *OP as an option to the ACCESS ADD
  63 </I>&gt;<i>command, and display levels by name in LIST if EXPERT is not set.  The
  64 </I>&gt;<i>user/Services dialogue would look something like this:
  65 </I>&gt;<i>
  66 </I>
  67 ] ... SNIP ... [
  68
  69 This sounds like something that would probably be best suited to an
  70 individual setting rather than a channel setting.  Perhaps it would
  71 also be wise to display both level &quot;types&quot; for those with the EXPERT
  72 mode set:
  73
  74 -&gt; *ChanServ* access #channel list
  75 -ChanServ- Num  Level  OP-Type Nick
  76 -ChanServ-   1     10  AOP     MyNick
  77 -ChanServ-   2      5  SOP     SomeNick
  78
  79 Also, (on a side note) those with expert mode not set might be
  80 limited from setting/using the more &quot;dangerous&quot; commands like:
  81 -&gt; *NickServ* SET KILL IMMED
  82
  83 Just a few ramblings,
  84 Kelmar K. Firesun
  85
  86
  87
  88
  89 ---------------------------------------------------------------
  90 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
  91 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
  92
  93
  94 </PRE>
  95
  96 <!--endarticle-->
  97     <HR>
  98     <P><UL>
  99         <!--threads-->
 100         <LI>Previous message: <A HREF="000535.html">[IRCServices] ACCESS and *OP
 101 </A></li>
 102         <LI>Next message: <A HREF="000538.html">[IRCServices] 4.4.x ETA
 103 </A></li>
 104          <LI> <B>Messages sorted by:</B>
 105               <a href="date.html#537">[ date ]</a>
 106               <a href="thread.html#537">[ thread ]</a>
 107               <a href="subject.html#537">[ subject ]</a>
 108               <a href="author.html#537">[ author ]</a>
 109          </LI>
 110        </UL>
 111
 112 </body></html>