]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2004/003013.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2004 / 003013.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] ChanServ suggestion
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ChanServ%20suggestion&In-Reply-To=E1BDWmm-0004ZU-VZ%40lon1-hub.mail.demon.net">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="003012.html">
11 <LINK REL="Next" HREF="003014.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] ChanServ suggestion</H1>
15 <B>M</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ChanServ%20suggestion&In-Reply-To=E1BDWmm-0004ZU-VZ%40lon1-hub.mail.demon.net"
17 TITLE="[IRCServices Coding] ChanServ suggestion">mark at ctcp.net
18 </A><BR>
19 <I>Tue Apr 13 16:12:27 PDT 2004</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003012.html">[IRCServices Coding] ChanServ suggestion
22 </A></li>
23 <LI>Next message: <A HREF="003014.html">[IRCServices Coding] ChanServ suggestion
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#3013">[ date ]</a>
27 <a href="thread.html#3013">[ thread ]</a>
28 <a href="subject.html#3013">[ subject ]</a>
29 <a href="author.html#3013">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Craig McLure wrote:
35 &gt;<i> I have asked about this before, and Andrew responded by
36 </I>&gt;<i> saying that this would be relativly redundant. The Access
37 </I>&gt;<i> changing is a 'one-off' event, generally an op would be able
38 </I>&gt;<i> to perform the mode changes if nessecery.
39 </I>
40 Since IIRC services performs some checks when adding a user to the access
41 list (e.g. checking for a registered nick), it should be a minimal change to
42 &quot;set mode if online&quot;. I suspect if there is sufficient support on list, this
43 might be thought about.
44
45 &gt;<i> Dont get me wrong thou, i still think this would be a nice
46 </I>&gt;<i> feature. (I may even concider looking into making a module to
47 </I>&gt;<i> do this at a later date.)
48 </I>
49 A patch might be a better option since a module seems overkill for this and
50 would likely involve a much higher overhead than checking during the &quot;add&quot;
51 process.
52
53 M.
54
55
56
57
58 </PRE>
59
60 <!--endarticle-->
61 <HR>
62 <P><UL>
63 <!--threads-->
64 <LI>Previous message: <A HREF="003012.html">[IRCServices Coding] ChanServ suggestion
65 </A></li>
66 <LI>Next message: <A HREF="003014.html">[IRCServices Coding] ChanServ suggestion
67 </A></li>
68 <LI> <B>Messages sorted by:</B>
69 <a href="date.html#3013">[ date ]</a>
70 <a href="thread.html#3013">[ thread ]</a>
71 <a href="subject.html#3013">[ subject ]</a>
72 <a href="author.html#3013">[ author ]</a>
73 </LI>
74 </UL>
75
76 </body></html>