projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices] ChanServ OP/DEOP/etc Suggestion | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20OP/DEOP/etc%20Suggestion&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="002771.html"> | |
| 11 | <LINK REL="Next" HREF="002778.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices] ChanServ OP/DEOP/etc Suggestion</H1> | |
| 15 | <B>Martin Pels</B> | |
| 16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20ChanServ%20OP/DEOP/etc%20Suggestion&In-Reply-To=" | |
| 17 | TITLE="[IRCServices] ChanServ OP/DEOP/etc Suggestion">martinpels at hotmail.com | |
| 18 | </A><BR> | |
| 19 | <I>Wed Feb 13 23:59:00 PST 2002</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="002771.html">[IRCServices] Suggestion wrt Service Admin rights | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="002778.html">[IRCServices] ChanServ OP/DEOP/etc Suggestion | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#2777">[ date ]</a> | |
| 27 | <a href="thread.html#2777">[ thread ]</a> | |
| 28 | <a href="subject.html#2777">[ subject ]</a> | |
| 29 | <a href="author.html#2777">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>I think it would be a good idea to make the ChanServ OP, DEOP, etc. commands | |
| 35 | available to users in the Services Oper and Admin list for every channel. | |
| 36 | Users in these lists can allready use the OperServ MODE and KICK commands, | |
| 37 | why not give them the ability to do the same with ChanServ? | |
| 38 | ||
| 39 | Another option is to give Services Operators/Admins acceslevel 100 or 1000 | |
| 40 | on every channel. | |
| 41 | Using the latter they wouldn't have to do GETPASS first and then identify | |
| 42 | for the channel before they can change settings. | |
| 43 | ||
| 44 | </PRE> | |
| 45 | ||
| 46 | <!--endarticle--> | |
| 47 | <HR> | |
| 48 | <P><UL> | |
| 49 | <!--threads--> | |
| 50 | <LI>Previous message: <A HREF="002771.html">[IRCServices] Suggestion wrt Service Admin rights | |
| 51 | </A></li> | |
| 52 | <LI>Next message: <A HREF="002778.html">[IRCServices] ChanServ OP/DEOP/etc Suggestion | |
| 53 | </A></li> | |
| 54 | <LI> <B>Messages sorted by:</B> | |
| 55 | <a href="date.html#2777">[ date ]</a> | |
| 56 | <a href="thread.html#2777">[ thread ]</a> | |
| 57 | <a href="subject.html#2777">[ subject ]</a> | |
| 58 | <a href="author.html#2777">[ author ]</a> | |
| 59 | </LI> | |
| 60 | </UL> | |
| 61 | ||
| 62 | </body></html> |