]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001850.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001850.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] /notice??
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/notice%3F%3F&In-Reply-To=001401c0d827%246aecc580%248000a8c0%40girotek.com">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001849.html">
11 <LINK REL="Next" HREF="001851.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] /notice??</H1>
15 <B>Bryan Clark</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/notice%3F%3F&In-Reply-To=001401c0d827%246aecc580%248000a8c0%40girotek.com"
17 TITLE="[IRCServices] /notice??">bclark at bclark.yi.org
18 </A><BR>
19 <I>Wed May 9 03:48:00 PDT 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001849.html">[IRCServices] /notice??
22 </A></li>
23 <LI>Next message: <A HREF="001851.html">[IRCServices] Changing IRCD's
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1850">[ date ]</a>
27 <a href="thread.html#1850">[ thread ]</a>
28 <a href="subject.html#1850">[ subject ]</a>
29 <a href="author.html#1850">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>On Tue, 8 May 2001 21:28:54 -0400, ViPeR said:
35
36 [Regarding the ability to specify a nick in /nickserv identify]
37
38 &gt;<i> The idea
39 </I>&gt;<i> could work, but its a long way from the current IRCServices setup
40 </I>
41 Well, not as far off as you might think, if you think about how services
42 keeps track of channels a user has identified for .....
43
44 &gt;<i> and would
45 </I>&gt;<i> go more toward the idea of no access list for nicks, and nicks would
46 </I>become
47 &gt;<i> more like logins. (ie the stuff Andrew discussed about version 5)
48 </I>
49 For the record, I see access lists as a mixed blessing -- great if you
50 know how to use them, but a real pain if you have a lot of people who
51 think *@* is a nice thing to put in there. :P I think someone suggested
52 earlier that they be optional; that's probably the way to go.
53
54
55 </PRE>
56
57 <!--endarticle-->
58 <HR>
59 <P><UL>
60 <!--threads-->
61 <LI>Previous message: <A HREF="001849.html">[IRCServices] /notice??
62 </A></li>
63 <LI>Next message: <A HREF="001851.html">[IRCServices] Changing IRCD's
64 </A></li>
65 <LI> <B>Messages sorted by:</B>
66 <a href="date.html#1850">[ date ]</a>
67 <a href="thread.html#1850">[ thread ]</a>
68 <a href="subject.html#1850">[ subject ]</a>
69 <a href="author.html#1850">[ author ]</a>
70 </LI>
71 </UL>
72
73 </body></html>