]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices Coding] MemoServ suggestion | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20MemoServ%20suggestion&In-Reply-To=F253P74giJRMSFDQgq300011e9a%40hotmail.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="001121.html"> | |
11 | <LINK REL="Next" HREF="001125.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] MemoServ suggestion</H1> | |
15 | <B>RT.Mail at verizon.net</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20MemoServ%20suggestion&In-Reply-To=F253P74giJRMSFDQgq300011e9a%40hotmail.com" | |
17 | TITLE="[IRCServices Coding] MemoServ suggestion">RT.Mail at verizon.net | |
18 | </A><BR> | |
19 | <I>Sat Jul 20 11:18:30 PDT 2002</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001121.html">[IRCServices Coding] MemoServ suggestion | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001125.html">[IRCServices Coding] BUG on version 5 | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1122">[ date ]</a> | |
27 | <a href="thread.html#1122">[ thread ]</a> | |
28 | <a href="subject.html#1122">[ subject ]</a> | |
29 | <a href="author.html#1122">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Ok first off.. | |
35 | "But I don't agree with you calling it bloat... Maybe you meant | |
36 | feature | |
37 | bloat, but then so is an httpd for services, email confirmation of | |
38 | nicknames, or nick linking/grouping. So the argument goes both | |
39 | ways..." | |
40 | Email confirmation is needed to help prevent abuse of services and | |
41 | mass registration of nicks... Second thing is id also like to see a | |
42 | mass memo feature or maybe a 30 second delay on the logon | |
43 | news.Because nobody reads it as it is now. You may say thats the | |
44 | users problem however in the end it becomes the IRCop's problems. | |
45 | ||
46 | ||
47 | </PRE> | |
48 | ||
49 | <!--endarticle--> | |
50 | <HR> | |
51 | <P><UL> | |
52 | <!--threads--> | |
53 | <LI>Previous message: <A HREF="001121.html">[IRCServices Coding] MemoServ suggestion | |
54 | </A></li> | |
55 | <LI>Next message: <A HREF="001125.html">[IRCServices Coding] BUG on version 5 | |
56 | </A></li> | |
57 | <LI> <B>Messages sorted by:</B> | |
58 | <a href="date.html#1122">[ date ]</a> | |
59 | <a href="thread.html#1122">[ thread ]</a> | |
60 | <a href="subject.html#1122">[ subject ]</a> | |
61 | <a href="author.html#1122">[ author ]</a> | |
62 | </LI> | |
63 | </UL> | |
64 | ||
65 | </body></html> |