--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [IRCServices Coding] Mass memos
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Mass%20memos&In-Reply-To=">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002126.html">
+ <LINK REL="Next" HREF="002128.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[IRCServices Coding] Mass memos</H1>
+ <B>Saturn</B>
+ <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Mass%20memos&In-Reply-To="
+ TITLE="[IRCServices Coding] Mass memos">saturn at jetirc.net
+ </A><BR>
+ <I>Wed Aug 13 14:49:02 PDT 2003</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002126.html">[IRCServices Coding] Mass memos
+</A></li>
+ <LI>Next message: <A HREF="002128.html">[IRCServices Coding] Mass memos
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2127">[ date ]</a>
+ <a href="thread.html#2127">[ thread ]</a>
+ <a href="subject.html#2127">[ subject ]</a>
+ <a href="author.html#2127">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>M wrote:
+
+Saturn wrote:
+>><i> Can we reconsider adding a Mass memo function for the next release?
+</I>
+><i>I do not think services should include spam functionality. Spam is
+</I>><i>enough of a problem without adding features to make it easier to annoy
+</I>><i>users.
+</I>
+This is not spam, and should probably be only accessible by either Services
+Admins or Services OPs. The intention is to announce outages, important
+events, etc
+
+>><i> If not, or even if so... one thing puzzles me: In the /ns
+</I>>><i> list * command, the listings have occasional punctuation...
+</I>>><i> a ! or ? in front of the nick. There is nothing in the docs
+</I>>><i> anywhere that seems to address this, and I'm curious as to
+</I>>><i> what those mean.... an explanation would be helpful there too.
+</I>
+><i>Do an info on the nick. It will explain the purpose of the symbol
+</I>><i>(forbidden/noexpire).
+</I>
+I did come across that after sending the email to the group. Sadly, it
+provides no help whatsoever to the memo question.. but it did shed light on
+the question i asked.....
+
+>><i> Additionally, perhaps we can have some way to glag a nick
+</I>>><i> name as "Linked" -- not necessarily the Primary name, but the
+</I>>><i> linked nicks... liek another puntuation in the listing that
+</I>>><i> indicates linked names, so I can script around it, havign it
+</I>>><i> ignore the marked nicks....
+</I>
+><i>As an SA you can list links for a nick. A user has no need to determine
+</I>><i>links of other users.
+</I>
+Who decided that? you? Perhaps I would like my users to be able to see the
+links for each other... Either way the command is only useful when you
+have a "starting point" - a nick that you want to look up...
+
+>><i> the main reason nobody read the logonnews is that
+</I>>><i> 90% of the time for them, it is unchanged........
+</I>
+><i>That is why it includes a date and you should delete old news to avoid
+</I>><i>vast amounts of useless text. I assume you have a website, so you can
+</I>><i>use this to display information that you want people to be able to
+</I>><i>"keep".
+</I>
+Frankly, logonnews is useless, and most of my users and opers agree. It
+scrolls off too fast. Ideally, it shoudl have a delay to prevent it being
+lost in the system notices on connection. Maybe a 10 second delay beforee
+it flashes by, to give the user time to connect, etc, and then they might
+actually SEE it. Most users I know don't tend to make a habit of readin gth
+ebacklog in their status windows when they connect to the network......
+
+Anyhow these were just friendly suggestions, tryign to solve a problem I
+have. I don't plan to simply go "OK well, since one or two others out there
+think my ideas are dumb for them, obviously I ought to abandon them, because
+they MUST be dumb" That attitude is ignorant, and I think my suggestions
+had weight and merit. Your objections have merit too, but I see you did not
+suggest any useful alternatives or workarounds... Thanks for the input!
+
+><i>M.
+</I>
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002126.html">[IRCServices Coding] Mass memos
+</A></li>
+ <LI>Next message: <A HREF="002128.html">[IRCServices Coding] Mass memos
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2127">[ date ]</a>
+ <a href="thread.html#2127">[ thread ]</a>
+ <a href="subject.html#2127">[ subject ]</a>
+ <a href="author.html#2127">[ author ]</a>
+ </LI>
+ </UL>
+
+</body></html>
projects / irc.git / blobdiff