]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2003/003958.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2003 / 003958.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Chanserv forbid..
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Chanserv%20forbid..&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="003953.html">
11 <LINK REL="Next" HREF="003960.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Chanserv forbid..</H1>
15 <B>Craig Edwards</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Chanserv%20forbid..&In-Reply-To="
17 TITLE="[IRCServices] Chanserv forbid..">brain at brainbox.winbot.co.uk
18 </A><BR>
19 <I>Thu Jul 10 10:42:37 PDT 2003</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003953.html">[IRCServices] Chanserv forbid..
22 </A></li>
23 <LI>Next message: <A HREF="003960.html">[IRCServices] Chanserv forbid..
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#3958">[ date ]</a>
27 <a href="thread.html#3958">[ thread ]</a>
28 <a href="subject.html#3958">[ subject ]</a>
29 <a href="author.html#3958">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>it would be great if such a 'reason' parameter was optional, and filled with a null value if not specified. This way users can continue to use the old style of the command if they wish to, without having to memorize a new way of issuing the command, and people who want to specify reasons can.
35
36 &gt;&gt;<i> On Tue, 8 Jul 2003 17:13:21 -0300, Diego B. Contezini
37 </I>&gt;&gt;<i> it seems to me that nickserv and chanserv FORBID are designed for
38 </I>&gt;&gt;<i> nicks and channels in which something is wrong with the nick
39 </I>&gt;&gt;<i> or channel *name*, and not the person or group of people involved.
40 </I>&gt;&gt;<i>
41 </I>&gt;&gt;<i> Therefore, when using forbid, the reason for forbidding that
42 </I>&gt;&gt;<i> nickname/channel name should be obvious.
43 </I>&gt;<i>
44 </I>&gt;<i>On my network, we often have to forbid channels for reasons other than the
45 </I>&gt;<i>name. When I look at our forbidden list, I can't tell why half of them are
46 </I>&gt;<i>forbidden, and I have to check my IRC client logs. A reason would be great.
47 </I>&gt;<i>
48 </I>&gt;<i>-Ross
49 </I>&gt;<i>
50 </I>&gt;<i>*-----------------------------------*
51 </I>&gt;|<i> Tribes 1 &amp; 2 Chat Server Admin |
52 </I>&gt;|<i> Email: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">bytor at tribes2maps.com</A> |
53 </I>&gt;|<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">bytor at sierra.com</A> |
54 </I>&gt;|<i> Server: irc.dynamix.com Port 6667 |
55 </I>&gt;|<i> Visit <A HREF="http://www.Tribes2Maps.com">http://www.Tribes2Maps.com</A> |
56 </I>&gt;<i>*-----------------------------------*
57 </I>&gt;<i>
58 </I>&gt;<i>
59 </I>&gt;<i>------------------------------------------------------------------
60 </I>&gt;<i>To unsubscribe or change your subscription options, visit:
61 </I>&gt;<i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
62 </I>
63
64 </PRE>
65
66 <!--endarticle-->
67 <HR>
68 <P><UL>
69 <!--threads-->
70 <LI>Previous message: <A HREF="003953.html">[IRCServices] Chanserv forbid..
71 </A></li>
72 <LI>Next message: <A HREF="003960.html">[IRCServices] Chanserv forbid..
73 </A></li>
74 <LI> <B>Messages sorted by:</B>
75 <a href="date.html#3958">[ date ]</a>
76 <a href="thread.html#3958">[ thread ]</a>
77 <a href="subject.html#3958">[ subject ]</a>
78 <a href="author.html#3958">[ author ]</a>
79 </LI>
80 </UL>
81
82 </body></html>