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 Coding] OP/Voice upon identify | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20OP/Voice%20upon%20identify&In-Reply-To=3f513092.01677%40achurch.org"> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="002175.html"> | |
| 11 | <LINK REL="Next" HREF="002172.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] OP/Voice upon identify</H1> | |
| 15 | <B>Shaun Guth</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20OP/Voice%20upon%20identify&In-Reply-To=3f513092.01677%40achurch.org" | |
| 17 | TITLE="[IRCServices Coding] OP/Voice upon identify">l8nite at l8nite.net | |
| 18 | </A><BR> | |
| 19 | <I>Sat Aug 30 16:58:16 PDT 2003</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="002175.html">[IRCServices Coding] OP/Voice upon identify | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="002172.html">[IRCServices Coding] SETHOST, SENDMAIL and 'ns info all' | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#2730">[ date ]</a> | |
| 27 | <a href="thread.html#2730">[ thread ]</a> | |
| 28 | <a href="subject.html#2730">[ subject ]</a> | |
| 29 | <a href="author.html#2730">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>On Sun, 2003-08-31 at 01:16, Andrew Church wrote: | |
| 35 | ><i> Needless complexity. If you don't want yourself autoopped, then don't | |
| 36 | </I>><i> be an auto-op. It's that simple. | |
| 37 | </I> | |
| 38 | I disagree. In my case, I wanted to create a channel where there were | |
| 39 | no ops so users don't have to endure lame op-wars, etc. However, I did | |
| 40 | need to maintain a level of control over the channel to protect from | |
| 41 | extremely obnoxious behavior or lame bots, etc. By registering as | |
| 42 | founder of the channel I induced the unwanted 'auto-op' behavior. My | |
| 43 | only solution was to register another fake user to become channel | |
| 44 | founder and set their nick to noexpire. That to me seems like needless | |
| 45 | complexity. A simple check to see if the user wishes to be opped or not | |
| 46 | is not complex. | |
| 47 | ||
| 48 | Shaun | |
| 49 | ||
| 50 | ||
| 51 | </PRE> | |
| 52 | ||
| 53 | <!--endarticle--> | |
| 54 | <HR> | |
| 55 | <P><UL> | |
| 56 | <!--threads--> | |
| 57 | <LI>Previous message: <A HREF="002175.html">[IRCServices Coding] OP/Voice upon identify | |
| 58 | </A></li> | |
| 59 | <LI>Next message: <A HREF="002172.html">[IRCServices Coding] SETHOST, SENDMAIL and 'ns info all' | |
| 60 | </A></li> | |
| 61 | <LI> <B>Messages sorted by:</B> | |
| 62 | <a href="date.html#2730">[ date ]</a> | |
| 63 | <a href="thread.html#2730">[ thread ]</a> | |
| 64 | <a href="subject.html#2730">[ subject ]</a> | |
| 65 | <a href="author.html#2730">[ author ]</a> | |
| 66 | </LI> | |
| 67 | </UL> | |
| 68 | ||
| 69 | </body></html> |