[IRCServices] the idea of operflags

[Andrew Church]

>I've noticed that quite a lot of services packages now have, instead of a
>"levels" based system of oper access to services, (such as oper < services
>oper < services admin < services root), a "flags" system of access.
>
>This "flags" system is really very simple, commands (or groups of
>commands)
>each have flags that you must posess in order to use them.
>
>For example, there could be one flag for having admin access to forbid
>channels, another to drop/force register channels, another to set things
>like the channel password, and another to use 'sendpass'.

     I'm not quite sure how this is "simple" compared to the current
system...

>The benifits of this system are clear, much more finely tuned operator
>access to services according to job, greater access seperation, and a much
>more flexible services package overall.

     On the other hand, drawbacks include more complex configuration, more
complex code (meaning more potential bugs), and more annoyance when trying
to deal with people who can't get it set up right.

     Still, the issue of inflexibility in the current system has been
raised before, and I may consider modifying it to allow more customization
in version 5.1 or later.  I will not be making any changes in 5.0.

  --Andrew Church
    achurch at achurch.org
    http://achurch.org/