software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2004/004517.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=40f5f27a.75644%40achurch.org">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="004519.html">
  11    <LINK REL="Next"  HREF="004518.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Unreal modelock issue</H1>
  15     <B>Bergee</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Unreal%20modelock%20issue&In-Reply-To=40f5f27a.75644%40achurch.org"
  17        TITLE="[IRCServices] Unreal modelock issue">lordbergee at comcast.net
  18        </A><BR>
  19     <I>Wed Jul 14 20:13:53 PDT 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="004519.html">[IRCServices] Unreal modelock issue
  22 </A></li>
  23         <LI>Next message: <A HREF="004518.html">[IRCServices] Unreal modelock issue
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#4517">[ date ]</a>
  27               <a href="thread.html#4517">[ thread ]</a>
  28               <a href="subject.html#4517">[ subject ]</a>
  29               <a href="author.html#4517">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Andrew Church wrote:
  35 &gt;<i>      This has been brought up before, and I won't be changing this
  36 </I>&gt;<i> behavior; this is a classic case of DDTT.
  37 </I>
  38         Whoops, guess I didn't search hard enough then, my fault.  :)  I
  39 suppose that is true in terms of a solution.  I was really suggesting it
  40 because the IRCd won't let normal users set the mode and it followed to
  41 me that neither should services.  :)
  42
  43 Craig McLure wrote:
  44  &gt; This is questionable, and adds some complexity to services, imo, at
  45  &gt; the end of the day, if you can SET mlock +A and +O, then you can also
  46  &gt; unset it. making 'Only admin can set this mlock' code redundant.
  47
  48         I was actually trying to suggest that similar to how ChanServ treats
  49 +r, a normal user simply not be allowed to include modes O or A in the
  50 mode lock at all. :)
  51
  52 Bergee
  53
  54
  55 </PRE>
  56
  57 <!--endarticle-->
  58     <HR>
  59     <P><UL>
  60         <!--threads-->
  61         <LI>Previous message: <A HREF="004519.html">[IRCServices] Unreal modelock issue
  62 </A></li>
  63         <LI>Next message: <A HREF="004518.html">[IRCServices] Unreal modelock issue
  64 </A></li>
  65          <LI> <B>Messages sorted by:</B>
  66               <a href="date.html#4517">[ date ]</a>
  67               <a href="thread.html#4517">[ thread ]</a>
  68               <a href="subject.html#4517">[ subject ]</a>
  69               <a href="author.html#4517">[ author ]</a>
  70          </LI>
  71        </UL>
  72
  73 </body></html>