+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<HTML>
- <HEAD>
- <TITLE> [IRCServices] ACCESS and *OP
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ACCESS%20and%20%2AOP&In-Reply-To=">
- <META NAME="robots" CONTENT="index,nofollow">
- <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <LINK REL="Previous" HREF="000531.html">
- <LINK REL="Next" HREF="000534.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[IRCServices] ACCESS and *OP</H1>
- <B>Andrew Church</B>
- <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ACCESS%20and%20%2AOP&In-Reply-To="
- TITLE="[IRCServices] ACCESS and *OP">achurch at dragonfire.net
- </A><BR>
- <I>Sat May 13 01:37:19 PDT 2000</I>
- <P><UL>
- <LI>Previous message: <A HREF="000531.html">[IRCServices] IRC Services (fwd)
-</A></li>
- <LI>Next message: <A HREF="000534.html">[IRCServices] ACCESS and *OP
-</A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#533">[ date ]</a>
- <a href="thread.html#533">[ thread ]</a>
- <a href="subject.html#533">[ subject ]</a>
- <a href="author.html#533">[ author ]</a>
- </LI>
- </UL>
- <HR>
-<!--beginarticle-->
-<PRE>><i>How would everyone fell if we removed the ACCESS command and replaced it
-</I>><i>with AOP SOP etc? This would simplify things dramatically and I know it
-</I>><i>would affect those people who want very customisable channel access
-</I>><i>levels.
-</I>
- This is a bit late because I haven't had Internet access for the past
-two weeks (just moved to a new apartment), but here's my two cents on the
-subject.
-
- Without touching (yet) the subject of A/S/VOP, I'm very strongly
-against the removal of the ACCESS command. While I have to admit part of
-that is the fact that I created that system and happen to like it, there
-are a couple of other big problems that would crop up:
-
- 1) You don't just remove a feature without warning or everyone who's
-been using that feature gets screwed. Some people on the mailing list
-have already mentioned it, but there are people who are perfectly used to
-the current ACCESS command and in fact don't even know about AOP/SOP/etc.
-
- 2) Converting current channel databases to work without ACCESS would
-be a nightmare, and even in the best scenario some settings would be lost.
-Do you want to tell a user "we upgraded our software and now you can't do
-this anymore"?
-
- As for the addition of AOP/SOP/etc commands, I am not overly against
-them except inasmuch as they represent a "standard" that doesn't have to
-be a standard; I also remember quite well the numerous complaints that
-people found the level system difficult to use. On the other hand, I have
-come to detest the attitude of Microsoft (among others) to do their best
-to keep you ignorant even if you know what you're doing, and taking out
-the ACCESS command would be too close to that for my liking. What I would
-recommend is to add the *OP functions, either as commands or as
-alternatives for the ACCESS ADD level value, and have those functions in
-turn call ACCESS ADD with an appropriate level. Naturally, this would not
-work if the channel levels had been changed, but by adding an EXPERT
-channel option as someone else suggested and disallowing level changes
-without EXPERT set, AOP/SOP/etc become workable again under the ACCESS
-system.
-
- My personal preference is to use *OP as an option to the ACCESS ADD
-command, and display levels by name in LIST if EXPERT is not set. The
-user/Services dialogue would look something like this:
-
--> *ChanServ* access #channel add SomeNick sop
--ChanServ- SomeNick added to channel #channel access list as an auto-op.
--> *ChanServ* access #channel list
--ChanServ- Num Level Nick
--ChanServ- 1 SOP MyNick
--ChanServ- 2 AOP NotMyNick
--ChanServ- 3 AOP SomeNick
--> *ChanServ* access #channel list levels
--ChanServ- Num Level Nick
--ChanServ- 1 10 MyNick
--ChanServ- 2 6 NotMyNick // Anything from AOP to SOP-1 is "AOP"
--ChanServ- 3 5 SomeNick
--> *ChanServ* access #channel list aop
--ChanServ- Num Level Nick
--ChanServ- 2 AOP NotMyNick
--ChanServ- 3 AOP SomeNick
-
- Admittedly, the last examples are a bit questionable as they can let
-someone with the nick "levels" or "aop" hide from channel lists, but if
-that becomes a problem it's easy enough to forbid the nicknames/
-
- The EXPERT option might work something like this:
-
--> *ChanServ* levels #channel set memo 50
--ChanServ- The EXPERT option must be set to change access level settings.
--> *ChanServ* set #channel expert on
--ChanServ- The EXPERT option for #channel is now active.
--> *ChanServ* levels #channel set memo 50
--ChanServ- Level MEMO on channel #channel changed to 50.
--> *ChanServ* access #channel list
--ChanServ- Num Level Nick
--ChanServ- 1 10 MyNick
--ChanServ- 2 5 SomeNick
--> *ChanServ* access #channel list aop
--ChanServ- AOP setting is disabled when EXPERT is set.
--> *ChanServ* set #channel expert off
--ChanServ- Warning: Disabling EXPERT will erase all access level changes.
--ChanServ- Use SET #channel EXPERT OFF FORCE to disable EXPERT anyway.
--> *ChanServ* set #channel expert off force
--ChanServ- The EXPERT option for #channel has been disabled.
--> *ChanServ* access #channel list
--ChanServ- Num Level Nick
--ChanServ- 1 SOP MyNick
--ChanServ- 2 AOP SomeNick
-
- Incidentally, I could see *OP being done as a module which could be
-loaded or not at the server operator's choice. (Yes, I will try to get
-back onto that module thing RSN...)
-
- --Andrew Church
- <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at dragonfire.net</A>
- <A HREF="http://achurch.dragonfire.net/">http://achurch.dragonfire.net/</A>
-
----------------------------------------------------------------
-To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
-with "unsubscribe ircservices" in the body, without the quotes.
-
-
-</PRE>
-
-<!--endarticle-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="000531.html">[IRCServices] IRC Services (fwd)
-</A></li>
- <LI>Next message: <A HREF="000534.html">[IRCServices] ACCESS and *OP
-</A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#533">[ date ]</a>
- <a href="thread.html#533">[ thread ]</a>
- <a href="subject.html#533">[ subject ]</a>
- <a href="author.html#533">[ author ]</a>
- </LI>
- </UL>
-
-</body></html>
projects / irc.git / blobdiff