software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2004/003015.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] ChanServ suggestion
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ChanServ%20suggestion&In-Reply-To=000f01c4218f%242f2acab0%240500a8c0%40DIMITRI">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="003011.html">
  11    <LINK REL="Next"  HREF="003012.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] ChanServ suggestion</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ChanServ%20suggestion&In-Reply-To=000f01c4218f%242f2acab0%240500a8c0%40DIMITRI"
  17        TITLE="[IRCServices Coding] ChanServ suggestion">achurch at achurch.org
  18        </A><BR>
  19     <I>Wed Apr 14 10:10:06 PDT 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003011.html">[IRCServices Coding] ChanServ suggestion
  22 </A></li>
  23         <LI>Next message: <A HREF="003012.html">[IRCServices Coding] ChanServ suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#3015">[ date ]</a>
  27               <a href="thread.html#3015">[ thread ]</a>
  28               <a href="subject.html#3015">[ subject ]</a>
  29               <a href="author.html#3015">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i>Andrew I was wondering if it would be possible to make chanserv
  35 </I>&gt;<i>+v/h/o/a/q/etc a registered nick as soon as they are added to the access
  36 </I>&gt;<i>list, so the user doesn't have to rejoin the channel or re-identify for the
  37 </I>&gt;<i>change to take effect? And then obviously when the nick is removed from the
  38 </I>&gt;<i>channel's access list, the same applies with -v/h/o/a/q/etc...
  39 </I>
  40      As Craig mentioned, this has been brought up before, and I haven't
  41 implemented it because IMO it's not worth the complexity.  Yes, it's not a
  42 difficult change to make, but it also adds yet another privilege escalation
  43 path, and yet another potential place for bugs to crop up.  It's not worth
  44 it for a one-off event such as this.
  45
  46   --Andrew Church
  47     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
  48     <A HREF="http://achurch.org/">http://achurch.org/</A>
  49
  50
  51 </PRE>
  52
  53 <!--endarticle-->
  54     <HR>
  55     <P><UL>
  56         <!--threads-->
  57         <LI>Previous message: <A HREF="003011.html">[IRCServices Coding] ChanServ suggestion
  58 </A></li>
  59         <LI>Next message: <A HREF="003012.html">[IRCServices Coding] ChanServ suggestion
  60 </A></li>
  61          <LI> <B>Messages sorted by:</B>
  62               <a href="date.html#3015">[ date ]</a>
  63               <a href="thread.html#3015">[ thread ]</a>
  64               <a href="subject.html#3015">[ subject ]</a>
  65               <a href="author.html#3015">[ author ]</a>
  66          </LI>
  67        </UL>
  68
  69 </body></html>