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> 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: "Andrew Church" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>> | |
| 45 | To: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>> | |
| 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 | ><i> >dont entirely get rid of it though, its great for sharing the root if | |
| 52 | </I>need | |
| 53 | ><i> >be. | |
| 54 | </I>><i> >question: why dont you just allow multiple roots? | |
| 55 | </I>><i> | |
| 56 | </I>><i> I don't see why either of these are necessary. Use SU. | |
| 57 | </I>><i> | |
| 58 | </I>><i> >-backburn aka brandon jank | |
| 59 | </I>><i> >----- Original Message ----- | |
| 60 | </I>><i> >From: "Andrew Church" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>> | |
| 61 | </I>><i> >To: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>> | |
| 62 | </I>><i> >Sent: Monday, May 14, 2001 6:04 PM | |
| 63 | </I>><i> >Subject: [IRCServices] Does anyone use nested nick links? | |
| 64 | </I>><i> > | |
| 65 | </I>><i> > | |
| 66 | </I>><i> >> As the subject says, I'd like to know if anyone finds the nested | |
| 67 | </I>><i> >> link system in Services useful, or if it's unnecessary. I originally | |
| 68 | </I>><i> >> modeled the system after symbolic links on Unix (and other) | |
| 69 | </I>filesystems, | |
| 70 | ><i> >> but as this makes for added complexity and has in fact led to a number | |
| 71 | </I>><i> >> of bugs in the past as well as administrative difficulties. So if | |
| 72 | </I>><i> >> there's no need for having multiple levels of nicks, I'm planning to | |
| 73 | </I>><i> >> just remove that capability in version 5 and limit links to a single | |
| 74 | </I>><i> >> level. | |
| 75 | </I>><i> >> | |
| 76 | </I>><i> >> Note that the only case in which this makes a visible difference | |
| 77 | </I>is | |
| 78 | ><i> >> the following: | |
| 79 | </I>><i> >> * Register NickA | |
| 80 | </I>><i> >> * Register NickB | |
| 81 | </I>><i> >> * Link NickB to NickA | |
| 82 | </I>><i> >> * Register NickC | |
| 83 | </I>><i> >> * Link NickC to NickB | |
| 84 | </I>><i> >> * Unlink NickB from NickA | |
| 85 | </I>><i> >> * Change a setting on NickB | |
| 86 | </I>><i> >> In the nested (current) system, NickC would use the new setting for | |
| 87 | </I>><i> >> NickB set in the last step, while in a flat system, NickC would retain | |
| 88 | </I>><i> >> the original settings associated with nick A. I can see potential | |
| 89 | </I>cases | |
| 90 | ><i> >> where this functionality can be useful, but if no one is actually using | |
| 91 | </I>><i> >> links that way, then there's no real need to retain the functionality. | |
| 92 | </I>><i> >> | |
| 93 | </I>><i> >> So, opinions, please: do you need nested links? | |
| 94 | </I>><i> >> | |
| 95 | </I>><i> >> --Andrew Church | |
| 96 | </I>><i> >> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
| 97 | </I>><i> >> <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 98 | </I>><i> >> ----------------------------------------------------------- | |
| 99 | </I>><i> >> To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A> | |
| 100 | </I>><i> >> with the word UNSUBSCRIBE in the subject of the mail. | |
| 101 | </I>><i> >> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
| 102 | </I>><i> >> | |
| 103 | </I>><i> > | |
| 104 | </I>><i> >----------------------------------------------------------- | |
| 105 | </I>><i> >To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A> | |
| 106 | </I>><i> >with the word UNSUBSCRIBE in the subject of the mail. | |
| 107 | </I>><i> ><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
| 108 | </I>><i> | |
| 109 | </I>><i> --Andrew Church | |
| 110 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
| 111 | </I>><i> <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 112 | </I>><i> ----------------------------------------------------------- | |
| 113 | </I>><i> To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A> | |
| 114 | </I>><i> with the word UNSUBSCRIBE in the subject of the mail. | |
| 115 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
| 116 | </I>><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> |