1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] ACCESS and *OP
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ACCESS%20and%20%2AOP&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=
"000536.html">
11 <LINK REL=
"Next" HREF=
"000537.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] ACCESS and *OP
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ACCESS%20and%20%2AOP&In-Reply-To="
17 TITLE=
"[IRCServices] ACCESS and *OP">k.hawkes at zombies.force9.net
19 <I>Sat May
13 05:
53:
57 PDT
2000</I>
21 <LI>Previous message:
<A HREF=
"000536.html">AW: [IRCServices] ACCESS and *OP
23 <LI>Next message:
<A HREF=
"000537.html">[IRCServices] ACCESS and *OP
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#535">[ date ]
</a>
27 <a href=
"thread.html#535">[ thread ]
</a>
28 <a href=
"subject.html#535">[ subject ]
</a>
29 <a href=
"author.html#535">[ author ]
</a>
37 ><i> From: Andrew Church
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at dragonfire.net
</A>>
38 </I>><i> To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ender.shadowfire.org
</A>
39 </I>><i> Subject: [IRCServices] ACCESS and *OP
40 </I>><i> Date: Saturday, May
13,
2000 02:
37
42 </I>><i> >How would everyone fell if we removed the ACCESS command and replaced it
43 </I>><i> >with AOP SOP etc? This would simplify things dramatically and I know it
44 </I>><i> >would affect those people who want very customisable channel access
45 </I>><i> >levels.
47 </I>Personally I don't like that idea, ACCESS may be a little difficult for newer Users to Services, but I like many other Users have gotten to used to ACCESS.
49 Adding AOP/SOP/VOP along side ACCESS is good, that way you have
2 standards, one for those who don't like ACCESS and one for those who do.
53 </I>><i> My personal preference is to use *OP as an option to the ACCESS ADD
54 </I>><i> command, and display levels by name in LIST if EXPERT is not set. The
55 </I>><i> user/Services dialogue would look something like this:
57 </I>><i> -
> *ChanServ* access #channel add SomeNick sop
58 </I>><i> -ChanServ- SomeNick added to channel #channel access list as an auto-op.
59 </I>><i> -
> *ChanServ* access #channel list
60 </I>><i> -ChanServ- Num Level Nick
61 </I>><i> -ChanServ-
1 SOP MyNick
62 </I>><i> -ChanServ-
2 AOP NotMyNick
63 </I>><i> -ChanServ-
3 AOP SomeNick
64 </I>><i> -
> *ChanServ* access #channel list levels
65 </I>><i> -ChanServ- Num Level Nick
66 </I>><i> -ChanServ-
1 10 MyNick
67 </I>><i> -ChanServ-
2 6 NotMyNick // Anything from AOP to SOP-
1 is
"AOP
"
68 </I>><i> -ChanServ-
3 5 SomeNick
69 </I>><i> -
> *ChanServ* access #channel list aop
70 </I>><i> -ChanServ- Num Level Nick
71 </I>><i> -ChanServ-
2 AOP NotMyNick
72 </I>><i> -ChanServ-
3 AOP SomeNick
74 </I>><i> Admittedly, the last examples are a bit questionable as they can let
75 </I>><i> someone with the nick
"levels
" or
"aop
" hide from channel lists, but if
76 </I>><i> that becomes a problem it's easy enough to forbid the nicknames/
78 </I>><i> The EXPERT option might work something like this:
80 </I>><i> -
> *ChanServ* levels #channel set memo
50
81 </I>><i> -ChanServ- The EXPERT option must be set to change access level settings.
82 </I>><i> -
> *ChanServ* set #channel expert on
83 </I>><i> -ChanServ- The EXPERT option for #channel is now active.
84 </I>><i> -
> *ChanServ* levels #channel set memo
50
85 </I>><i> -ChanServ- Level MEMO on channel #channel changed to
50.
86 </I>><i> -
> *ChanServ* access #channel list
87 </I>><i> -ChanServ- Num Level Nick
88 </I>><i> -ChanServ-
1 10 MyNick
89 </I>><i> -ChanServ-
2 5 SomeNick
90 </I>><i> -
> *ChanServ* access #channel list aop
91 </I>><i> -ChanServ- AOP setting is disabled when EXPERT is set.
92 </I>><i> -
> *ChanServ* set #channel expert off
93 </I>><i> -ChanServ- Warning: Disabling EXPERT will erase all access level changes.
94 </I>><i> -ChanServ- Use SET #channel EXPERT OFF FORCE to disable EXPERT anyway.
95 </I>><i> -
> *ChanServ* set #channel expert off force
96 </I>><i> -ChanServ- The EXPERT option for #channel has been disabled.
97 </I>><i> -
> *ChanServ* access #channel list
98 </I>><i> -ChanServ- Num Level Nick
99 </I>><i> -ChanServ-
1 SOP MyNick
100 </I>><i> -ChanServ-
2 AOP SomeNick
102 </I>><i> Incidentally, I could see *OP being done as a module which could be
103 </I>><i> loaded or not at the server operator's choice. (Yes, I will try to get
104 </I>><i> back onto that module thing RSN...)
106 </I>Just a tiny thing here Andy, why have it set EXPERT on the channel?
107 Why not have a flag in NickServ for EXPERT-type MODE so if a User is a newbie then they don't need it, if not then they can set EXPERT which will just take a few of the 'safeties' away, like you have with some programs you can have Novice/Expert Modes, Novice typically protects from some things where Expert does not...
109 Anyhow that's my
2 pence.
113 ><i> --Andrew Church
114 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at dragonfire.net
</A>
115 </I>><i> <A HREF=
"http://achurch.dragonfire.net/">http://achurch.dragonfire.net/
</A>
117 </I>><i> ---------------------------------------------------------------
118 </I>><i> To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
119 </I>><i> with
"unsubscribe ircservices
" in the body, without the quotes.
126 <LI>Previous message:
<A HREF=
"000536.html">AW: [IRCServices] ACCESS and *OP
128 <LI>Next message:
<A HREF=
"000537.html">[IRCServices] ACCESS and *OP
130 <LI> <B>Messages sorted by:
</B>
131 <a href=
"date.html#535">[ date ]
</a>
132 <a href=
"thread.html#535">[ thread ]
</a>
133 <a href=
"subject.html#535">[ subject ]
</a>
134 <a href=
"author.html#535">[ author ]
</a>
projects / irc.git / blob