software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2004/004518.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Unreal modelock issue
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Unreal%20modelock%20issue&In-Reply-To=40F5F671.9050700%40comcast.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="004517.html">
  11    <LINK REL="Next"  HREF="004514.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Unreal modelock issue</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Unreal%20modelock%20issue&In-Reply-To=40F5F671.9050700%40comcast.net"
  17        TITLE="[IRCServices] Unreal modelock issue">achurch at achurch.org
  18        </A><BR>
  19     <I>Thu Jul 15 12:25:16 PDT 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="004517.html">[IRCServices] Unreal modelock issue
  22 </A></li>
  23         <LI>Next message: <A HREF="004514.html">[IRCServices] Unreal modelock issue
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#4518">[ date ]</a>
  27               <a href="thread.html#4518">[ thread ]</a>
  28               <a href="subject.html#4518">[ subject ]</a>
  29               <a href="author.html#4518">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> &gt; This is questionable, and adds some complexity to services, imo, at
  35 </I>&gt;<i> &gt; the end of the day, if you can SET mlock +A and +O, then you can also
  36 </I>&gt;<i> &gt; unset it. making 'Only admin can set this mlock' code redundant.
  37 </I>&gt;<i>
  38 </I>&gt;<i>     I was actually trying to suggest that similar to how ChanServ treats
  39 </I>&gt;<i>+r, a normal user simply not be allowed to include modes O or A in the
  40 </I>&gt;<i>mode lock at all. :)
  41 </I>
  42      Which, as Craig says, requires more complexity than the current code
  43 (which doesn't differentiate between opers and regular users at all).
  44 This is my main technical objection to adding such a feature--the added
  45 complexity outweighs the (negligible) benefit provided.
  46
  47   --Andrew Church
  48     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
  49     <A HREF="http://achurch.org/">http://achurch.org/</A>
  50
  51
  52 </PRE>
  53
  54 <!--endarticle-->
  55     <HR>
  56     <P><UL>
  57         <!--threads-->
  58         <LI>Previous message: <A HREF="004517.html">[IRCServices] Unreal modelock issue
  59 </A></li>
  60         <LI>Next message: <A HREF="004514.html">[IRCServices] Unreal modelock issue
  61 </A></li>
  62          <LI> <B>Messages sorted by:</B>
  63               <a href="date.html#4518">[ date ]</a>
  64               <a href="thread.html#4518">[ thread ]</a>
  65               <a href="subject.html#4518">[ subject ]</a>
  66               <a href="author.html#4518">[ author ]</a>
  67          </LI>
  68        </UL>
  69
  70 </body></html>