software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/1999/000158.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Channel Successor
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Channel%20Successor&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="000156.html">
  11    <LINK REL="Next"  HREF="000160.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Channel Successor</H1>
  15     <B>Yusuf Iskenderoglu</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Channel%20Successor&In-Reply-To="
  17        TITLE="[IRCServices] Channel Successor">uhc0 at rz.uni-karlsruhe.de
  18        </A><BR>
  19     <I>Thu Sep 30 14:22:30 PDT 1999</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000156.html">Re(2): [IRCServices] Greetings
  22 </A></li>
  23         <LI>Next message: <A HREF="000160.html">[IRCServices] Modules
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#158">[ date ]</a>
  27               <a href="thread.html#158">[ thread ]</a>
  28               <a href="subject.html#158">[ subject ]</a>
  29               <a href="author.html#158">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>
  35 Hello,
  36
  37 I had some questions about Channel Successor setting.
  38 It is good to be able to set a successor for a channel, but
  39 even though one might be set, the successor has no rights while
  40 the founder's nickname persists.
  41
  42 I wanted to say, that e.g. the successor does not get autoopped, nor
  43 the successor can use other ChanServ commands.
  44 This results in having to add the successor to the access list, but the founder's
  45 nickname does not need to be in the access list.
  46
  47 What I am going to suggest is, to implement another level, an access level :
  48 successor level.
  49 Using this, the founder might use
  50 /chanserv levels #channel set set successor
  51 /chanserv levels #channel set clear successor
  52 To enable several commands to the successor.
  53
  54 And, therefore the successor level should be a level between 9999 and founder. To
  55 ensure that the successor can use &quot;normal&quot; chanserv commands.
  56
  57 regards;
  58
  59 ---------------------------------
  60 Yusuf Iskenderoglu
  61 eMail : <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at rz.uni-karlsruhe.de</A>
  62 ICQ : 20587464
  63 ---------------------------------
  64
  65 ---------------------------------------------------------------
  66 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
  67 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
  68
  69 </PRE>
  70
  71 <!--endarticle-->
  72     <HR>
  73     <P><UL>
  74         <!--threads-->
  75         <LI>Previous message: <A HREF="000156.html">Re(2): [IRCServices] Greetings
  76 </A></li>
  77         <LI>Next message: <A HREF="000160.html">[IRCServices] Modules
  78 </A></li>
  79          <LI> <B>Messages sorted by:</B>
  80               <a href="date.html#158">[ date ]</a>
  81               <a href="thread.html#158">[ thread ]</a>
  82               <a href="subject.html#158">[ subject ]</a>
  83               <a href="author.html#158">[ author ]</a>
  84          </LI>
  85        </UL>
  86
  87 </body></html>