]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2004/004243.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2004 / 004243.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=20040417210247.44991.qmail%40web25109.mail.ukl.yahoo.com">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="004241.html">
11 <LINK REL="Next" HREF="004242.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] the idea of operflags</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20the%20idea%20of%20operflags&In-Reply-To=20040417210247.44991.qmail%40web25109.mail.ukl.yahoo.com"
17 TITLE="[IRCServices] the idea of operflags">achurch at achurch.org
18 </A><BR>
19 <I>Sun Apr 18 08:53:58 PDT 2004</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="004241.html">[IRCServices] the idea of operflags
22 </A></li>
23 <LI>Next message: <A HREF="004242.html">[IRCServices] Chanserv UNBAN Bug
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#4243">[ date ]</a>
27 <a href="thread.html#4243">[ thread ]</a>
28 <a href="subject.html#4243">[ subject ]</a>
29 <a href="author.html#4243">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i>I've noticed that quite a lot of services packages now have, instead of a
35 </I>&gt;<i>&quot;levels&quot; based system of oper access to services, (such as oper &lt; services
36 </I>&gt;<i>oper &lt; services admin &lt; services root), a &quot;flags&quot; system of access.
37 </I>&gt;<i>
38 </I>&gt;<i>This &quot;flags&quot; system is really very simple, commands (or groups of
39 </I>&gt;<i>commands)
40 </I>&gt;<i>each have flags that you must posess in order to use them.
41 </I>&gt;<i>
42 </I>&gt;<i>For example, there could be one flag for having admin access to forbid
43 </I>&gt;<i>channels, another to drop/force register channels, another to set things
44 </I>&gt;<i>like the channel password, and another to use 'sendpass'.
45 </I>
46 I'm not quite sure how this is &quot;simple&quot; compared to the current
47 system...
48
49 &gt;<i>The benifits of this system are clear, much more finely tuned operator
50 </I>&gt;<i>access to services according to job, greater access seperation, and a much
51 </I>&gt;<i>more flexible services package overall.
52 </I>
53 On the other hand, drawbacks include more complex configuration, more
54 complex code (meaning more potential bugs), and more annoyance when trying
55 to deal with people who can't get it set up right.
56
57 Still, the issue of inflexibility in the current system has been
58 raised before, and I may consider modifying it to allow more customization
59 in version 5.1 or later. I will not be making any changes in 5.0.
60
61 --Andrew Church
62 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
63 <A HREF="http://achurch.org/">http://achurch.org/</A>
64
65
66 </PRE>
67
68 <!--endarticle-->
69 <HR>
70 <P><UL>
71 <!--threads-->
72 <LI>Previous message: <A HREF="004241.html">[IRCServices] the idea of operflags
73 </A></li>
74 <LI>Next message: <A HREF="004242.html">[IRCServices] Chanserv UNBAN Bug
75 </A></li>
76 <LI> <B>Messages sorted by:</B>
77 <a href="date.html#4243">[ date ]</a>
78 <a href="thread.html#4243">[ thread ]</a>
79 <a href="subject.html#4243">[ subject ]</a>
80 <a href="author.html#4243">[ author ]</a>
81 </LI>
82 </UL>
83
84 </body></html>