software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000497.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Services Admin : Global Access to Channel Settings
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%20Admin%20%3A%20Global%20Access%20to%20Channel%20Settings&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="000487.html">
  11    <LINK REL="Next"  HREF="000498.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Services Admin : Global Access to Channel Settings</H1>
  15     <B>Mark Hetherington</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%20Admin%20%3A%20Global%20Access%20to%20Channel%20Settings&In-Reply-To="
  17        TITLE="[IRCServices Coding] Services Admin : Global Access to Channel Settings">mark at ctcp.net
  18        </A><BR>
  19     <I>Tue Apr  9 15:59:58 PDT 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000487.html">[IRCServices Coding] Database Module
  22 </A></li>
  23         <LI>Next message: <A HREF="000498.html">[IRCServices Coding] Services Admin : Global Access to Channel Settings
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#497">[ date ]</a>
  27               <a href="thread.html#497">[ thread ]</a>
  28               <a href="subject.html#497">[ subject ]</a>
  29               <a href="author.html#497">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Adrian Cantrill wrote:
  35 &gt;<i> Yus... one viewpoint... I tend to go with the flip side.. that service
  36 </I>&gt;<i> admin should have 100% access to all channels etc... but I just watched
  37 </I>&gt;<i> to check if it was a intentional design decision.
  38 </I>&gt;<i>
  39 </I>&gt;<i> Maybe have this as a option though? Services as a whole will be more
  40 </I>&gt;<i> flexible then.
  41 </I>
  42 AIUI Services is not trying to be &quot;Big Brother&quot; and is there to provide
  43 protection to users as well as assistance to those that run the network so
  44 I don't really see such a thing becoming an option.
  45
  46 Why would you want to manage the access list of somebody else's channel
  47 anyway?
  48
  49 I think if you had and used the power you would find affected channels
  50 would swiftly relocate.
  51
  52 Look at the currently available support to remove the ability of users to
  53 register channels. In such an environment a services admin/root would have
  54 to register channels on demand so a services admin/root would become
  55 founder and would have full rights to the access list. See CSEnableRegister
  56 in modules.conf for more information.
  57
  58 --
  59 Mark.
  60
  61
  62
  63 </PRE>
  64
  65 <!--endarticle-->
  66     <HR>
  67     <P><UL>
  68         <!--threads-->
  69         <LI>Previous message: <A HREF="000487.html">[IRCServices Coding] Database Module
  70 </A></li>
  71         <LI>Next message: <A HREF="000498.html">[IRCServices Coding] Services Admin : Global Access to Channel Settings
  72 </A></li>
  73          <LI> <B>Messages sorted by:</B>
  74               <a href="date.html#497">[ date ]</a>
  75               <a href="thread.html#497">[ thread ]</a>
  76               <a href="subject.html#497">[ subject ]</a>
  77               <a href="author.html#497">[ author ]</a>
  78          </LI>
  79        </UL>
  80
  81 </body></html>