]> jfr.im git - irc.git/blame - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000285.html
init
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 000285.html
CommitLineData
3bd189cb
JR
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2<HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] More bugs and suggestions for Version 5.0
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20More%20bugs%20and%20suggestions%20for%20Version%205.0&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="000284.html">
11 <LINK REL="Next" HREF="000286.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] More bugs and suggestions for Version 5.0</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20More%20bugs%20and%20suggestions%20for%20Version%205.0&In-Reply-To="
17 TITLE="[IRCServices Coding] More bugs and suggestions for Version 5.0">achurch at achurch.org
18 </A><BR>
19 <I>Fri Feb 15 23:53:44 PST 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000284.html">[IRCServices Coding] Services 5.0 - NickServ register text suggestion
22</A></li>
23 <LI>Next message: <A HREF="000286.html">[IRCServices Coding] More bugs and suggestions for Version 5.0
24</A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#285">[ date ]</a>
27 <a href="thread.html#285">[ thread ]</a>
28 <a href="subject.html#285">[ subject ]</a>
29 <a href="author.html#285">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33<!--beginarticle-->
34<PRE>&gt;&gt;<i> I see your point, and yes, an ID alias would be nice, but my personal
35</I>&gt;&gt;<i> feeling is that aliases are not a good thing (tm) :). If you
36</I>&gt;&gt;<i> really want the
37</I>&gt;&gt;<i> ID alias - make a wrapper for the IDENTIFY function.
38</I>&gt;<i>
39</I>&gt;<i>As I said in my post, I already have my own version of ID in each version
40</I>&gt;<i>of services we use. I agree that aliases in general are not a good thing as
41</I>&gt;<i>I said previously, I just thought this one was something that might be
42</I>&gt;<i>useful to have in the main distribution. After all, there is already
43</I>&gt;<i>SIDENTIFY which is, to all intents and purposes, an alias for IDENTIFY.
44</I>
45 The only reason it's there is because some ircd (Bahamut?) has it
46hard-coded in. If you want something shorter, write an alias in your client.
47
48 --Andrew Church
49 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
50 <A HREF="http://achurch.org/">http://achurch.org/</A>
51
52</PRE>
53
54<!--endarticle-->
55 <HR>
56 <P><UL>
57 <!--threads-->
58 <LI>Previous message: <A HREF="000284.html">[IRCServices Coding] Services 5.0 - NickServ register text suggestion
59</A></li>
60 <LI>Next message: <A HREF="000286.html">[IRCServices Coding] More bugs and suggestions for Version 5.0
61</A></li>
62 <LI> <B>Messages sorted by:</B>
63 <a href="date.html#285">[ date ]</a>
64 <a href="thread.html#285">[ thread ]</a>
65 <a href="subject.html#285">[ subject ]</a>
66 <a href="author.html#285">[ author ]</a>
67 </LI>
68 </UL>
69
70</body></html>