]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001857.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001857.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> Multiple roots (was Re: [IRCServices] Does anyone use nested nick links?)
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=Multiple%20roots%20%28was%20Re%3A%20%5BIRCServices%5D%20Does%20anyone%20use%20nested%20nick%20links%3F%29&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="001856.html">
11 <LINK REL="Next" HREF="001860.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>Multiple roots (was Re: [IRCServices] Does anyone use nested nick links?)</H1>
15 <B>Strider</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=Multiple%20roots%20%28was%20Re%3A%20%5BIRCServices%5D%20Does%20anyone%20use%20nested%20nick%20links%3F%29&In-Reply-To="
17 TITLE="Multiple roots (was Re: [IRCServices] Does anyone use nested nick links?)">strider at chatcircuit.com
18 </A><BR>
19 <I>Tue May 15 07:41:00 PDT 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001856.html">Multiple roots (was Re: [IRCServices] Does anyone use nested nick links?)
22 </A></li>
23 <LI>Next message: <A HREF="001860.html">Multiple roots (was Re: [IRCServices] Does anyone use nested nick links?)
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1857">[ date ]</a>
27 <a href="thread.html#1857">[ thread ]</a>
28 <a href="subject.html#1857">[ subject ]</a>
29 <a href="author.html#1857">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>I only use one level of linking...never really considered multiple levels,
35 all my extra nicks link back to one. As for multiple roots...the SU command
36 is extremely helpful and I feel is more secure.
37
38 Beau (Strider) Steward
39 chatcircuit administrator and 6bit band member
40 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">strider at chatcircuit.com</A> www.chatcircuit.com
41 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircadmin at chatcircuit.com</A> irc.chatcircuit.com
42 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">strider at 6bit.net</A> www.6bit.net
43 ----- Original Message -----
44 From: &quot;Andrew Church&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>&gt;
45 To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>&gt;
46 Sent: Monday, May 14, 2001 9:35 PM
47 Subject: Multiple roots (was Re: [IRCServices] Does anyone use nested nick
48 links?)
49
50
51 &gt;<i> &gt;dont entirely get rid of it though, its great for sharing the root if
52 </I>need
53 &gt;<i> &gt;be.
54 </I>&gt;<i> &gt;question: why dont you just allow multiple roots?
55 </I>&gt;<i>
56 </I>&gt;<i> I don't see why either of these are necessary. Use SU.
57 </I>&gt;<i>
58 </I>&gt;<i> &gt;-backburn aka brandon jank
59 </I>&gt;<i> &gt;----- Original Message -----
60 </I>&gt;<i> &gt;From: &quot;Andrew Church&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>&gt;
61 </I>&gt;<i> &gt;To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>&gt;
62 </I>&gt;<i> &gt;Sent: Monday, May 14, 2001 6:04 PM
63 </I>&gt;<i> &gt;Subject: [IRCServices] Does anyone use nested nick links?
64 </I>&gt;<i> &gt;
65 </I>&gt;<i> &gt;
66 </I>&gt;<i> &gt;&gt; As the subject says, I'd like to know if anyone finds the nested
67 </I>&gt;<i> &gt;&gt; link system in Services useful, or if it's unnecessary. I originally
68 </I>&gt;<i> &gt;&gt; modeled the system after symbolic links on Unix (and other)
69 </I>filesystems,
70 &gt;<i> &gt;&gt; but as this makes for added complexity and has in fact led to a number
71 </I>&gt;<i> &gt;&gt; of bugs in the past as well as administrative difficulties. So if
72 </I>&gt;<i> &gt;&gt; there's no need for having multiple levels of nicks, I'm planning to
73 </I>&gt;<i> &gt;&gt; just remove that capability in version 5 and limit links to a single
74 </I>&gt;<i> &gt;&gt; level.
75 </I>&gt;<i> &gt;&gt;
76 </I>&gt;<i> &gt;&gt; Note that the only case in which this makes a visible difference
77 </I>is
78 &gt;<i> &gt;&gt; the following:
79 </I>&gt;<i> &gt;&gt; * Register NickA
80 </I>&gt;<i> &gt;&gt; * Register NickB
81 </I>&gt;<i> &gt;&gt; * Link NickB to NickA
82 </I>&gt;<i> &gt;&gt; * Register NickC
83 </I>&gt;<i> &gt;&gt; * Link NickC to NickB
84 </I>&gt;<i> &gt;&gt; * Unlink NickB from NickA
85 </I>&gt;<i> &gt;&gt; * Change a setting on NickB
86 </I>&gt;<i> &gt;&gt; In the nested (current) system, NickC would use the new setting for
87 </I>&gt;<i> &gt;&gt; NickB set in the last step, while in a flat system, NickC would retain
88 </I>&gt;<i> &gt;&gt; the original settings associated with nick A. I can see potential
89 </I>cases
90 &gt;<i> &gt;&gt; where this functionality can be useful, but if no one is actually using
91 </I>&gt;<i> &gt;&gt; links that way, then there's no real need to retain the functionality.
92 </I>&gt;<i> &gt;&gt;
93 </I>&gt;<i> &gt;&gt; So, opinions, please: do you need nested links?
94 </I>&gt;<i> &gt;&gt;
95 </I>&gt;<i> &gt;&gt; --Andrew Church
96 </I>&gt;<i> &gt;&gt; <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
97 </I>&gt;<i> &gt;&gt; <A HREF="http://achurch.org/">http://achurch.org/</A>
98 </I>&gt;<i> &gt;&gt; -----------------------------------------------------------
99 </I>&gt;<i> &gt;&gt; To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A>
100 </I>&gt;<i> &gt;&gt; with the word UNSUBSCRIBE in the subject of the mail.
101 </I>&gt;<i> &gt;&gt; <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
102 </I>&gt;<i> &gt;&gt;
103 </I>&gt;<i> &gt;
104 </I>&gt;<i> &gt;-----------------------------------------------------------
105 </I>&gt;<i> &gt;To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A>
106 </I>&gt;<i> &gt;with the word UNSUBSCRIBE in the subject of the mail.
107 </I>&gt;<i> &gt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
108 </I>&gt;<i>
109 </I>&gt;<i> --Andrew Church
110 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
111 </I>&gt;<i> <A HREF="http://achurch.org/">http://achurch.org/</A>
112 </I>&gt;<i> -----------------------------------------------------------
113 </I>&gt;<i> To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A>
114 </I>&gt;<i> with the word UNSUBSCRIBE in the subject of the mail.
115 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
116 </I>&gt;<i>
117 </I>
118
119 </PRE>
120
121 <!--endarticle-->
122 <HR>
123 <P><UL>
124 <!--threads-->
125 <LI>Previous message: <A HREF="001856.html">Multiple roots (was Re: [IRCServices] Does anyone use nested nick links?)
126 </A></li>
127 <LI>Next message: <A HREF="001860.html">Multiple roots (was Re: [IRCServices] Does anyone use nested nick links?)
128 </A></li>
129 <LI> <B>Messages sorted by:</B>
130 <a href="date.html#1857">[ date ]</a>
131 <a href="thread.html#1857">[ thread ]</a>
132 <a href="subject.html#1857">[ subject ]</a>
133 <a href="author.html#1857">[ author ]</a>
134 </LI>
135 </UL>
136
137 </body></html>