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

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] the idea of operflags
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20the%20idea%20of%20operflags&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="004250.html">
  11    <LINK REL="Next"  HREF="004243.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] the idea of operflags</H1>
  15     <B>Ashen</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20the%20idea%20of%20operflags&In-Reply-To="
  17        TITLE="[IRCServices] the idea of operflags">accountnamehere at yahoo.co.uk
  18        </A><BR>
  19     <I>Sat Apr 17 14:02:47 PDT 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="004250.html">[IRCServices] Chanserv UNBAN Bug
  22 </A></li>
  23         <LI>Next message: <A HREF="004243.html">[IRCServices] the idea of operflags
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#4241">[ date ]</a>
  27               <a href="thread.html#4241">[ thread ]</a>
  28               <a href="subject.html#4241">[ subject ]</a>
  29               <a href="author.html#4241">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>I've noticed that quite a lot of services packages now have, instead of a
  35 &quot;levels&quot; based system of oper access to services, (such as oper &lt; services
  36 oper &lt; services admin &lt; services root), a &quot;flags&quot; system of access.
  37
  38 This &quot;flags&quot; system is really very simple, commands (or groups of
  39 commands)
  40 each have flags that you must posess in order to use them.
  41
  42 For example, there could be one flag for having admin access to forbid
  43 channels, another to drop/force register channels, another to set things
  44 like the channel password, and another to use 'sendpass'.
  45
  46 The benifits of this system are clear, much more finely tuned operator
  47 access to services according to job, greater access seperation, and a much
  48 more flexible services package overall.
  49
  50 Are there any plans to implement such a feature into ircservices?
  51 Other packages are already implementing it, and it's a really nice feature
  52 a lot of us would like to see.
  53
  54 -Ashen
  55
  56
  57
  58
  59
  60 ____________________________________________________________
  61 Yahoo! Messenger - Communicate instantly...&quot;Ping&quot;
  62 your friends today! Download Messenger Now
  63 <A HREF="http://uk.messenger.yahoo.com/download/index.html">http://uk.messenger.yahoo.com/download/index.html</A>
  64
  65
  66 </PRE>
  67
  68 <!--endarticle-->
  69     <HR>
  70     <P><UL>
  71         <!--threads-->
  72         <LI>Previous message: <A HREF="004250.html">[IRCServices] Chanserv UNBAN Bug
  73 </A></li>
  74         <LI>Next message: <A HREF="004243.html">[IRCServices] the idea of operflags
  75 </A></li>
  76          <LI> <B>Messages sorted by:</B>
  77               <a href="date.html#4241">[ date ]</a>
  78               <a href="thread.html#4241">[ thread ]</a>
  79               <a href="subject.html#4241">[ subject ]</a>
  80               <a href="author.html#4241">[ author ]</a>
  81          </LI>
  82        </UL>
  83
  84 </body></html>