software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/002127.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Mass memos
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Mass%20memos&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="002126.html">
  11    <LINK REL="Next"  HREF="002128.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Mass memos</H1>
  15     <B>Saturn</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Mass%20memos&In-Reply-To="
  17        TITLE="[IRCServices Coding] Mass memos">saturn at jetirc.net
  18        </A><BR>
  19     <I>Wed Aug 13 14:49:02 PDT 2003</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002126.html">[IRCServices Coding] Mass memos
  22 </A></li>
  23         <LI>Next message: <A HREF="002128.html">[IRCServices Coding] Mass memos
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2127">[ date ]</a>
  27               <a href="thread.html#2127">[ thread ]</a>
  28               <a href="subject.html#2127">[ subject ]</a>
  29               <a href="author.html#2127">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>M wrote:
  35
  36 Saturn wrote:
  37 &gt;&gt;<i> Can we reconsider adding a Mass memo function for the next release?
  38 </I>
  39 &gt;<i>I do not think services should include spam functionality. Spam is
  40 </I>&gt;<i>enough of a problem without adding features to make it easier to annoy
  41 </I>&gt;<i>users.
  42 </I>
  43 This is not spam, and should probably be only accessible by either Services
  44 Admins or Services OPs.  The intention is to announce outages, important
  45 events, etc
  46
  47 &gt;&gt;<i> If not, or even if so... one thing puzzles me:  In the /ns
  48 </I>&gt;&gt;<i> list *  command, the listings have occasional punctuation...
  49 </I>&gt;&gt;<i> a ! or ? in front of the nick. There is nothing in the docs
  50 </I>&gt;&gt;<i> anywhere that seems to address this, and I'm curious as to
  51 </I>&gt;&gt;<i> what those mean.... an explanation would be helpful there too.
  52 </I>
  53 &gt;<i>Do an info on the nick. It will explain the purpose of the symbol
  54 </I>&gt;<i>(forbidden/noexpire).
  55 </I>
  56 I did come across that after sending the email to the group.  Sadly, it
  57 provides no help whatsoever to the memo question.. but it did shed light on
  58 the question i asked.....
  59
  60 &gt;&gt;<i> Additionally, perhaps we can have some way to glag a nick
  61 </I>&gt;&gt;<i> name as &quot;Linked&quot; -- not necessarily the Primary name, but the
  62 </I>&gt;&gt;<i> linked nicks... liek another puntuation in the listing that
  63 </I>&gt;&gt;<i> indicates linked names, so I can script around it, havign it
  64 </I>&gt;&gt;<i> ignore the marked nicks....
  65 </I>
  66 &gt;<i>As an SA you can list links for a nick. A user has no need to determine
  67 </I>&gt;<i>links of other users.
  68 </I>
  69 Who decided that? you? Perhaps I would like my users to be able to see the
  70 links for each other...   Either way the command is only useful when you
  71 have a &quot;starting point&quot; - a nick that you want to look up...
  72
  73 &gt;&gt;<i> the main reason nobody read the logonnews is that
  74 </I>&gt;&gt;<i> 90% of the time for them, it is unchanged........
  75 </I>
  76 &gt;<i>That is why it includes a date and you should delete old news to avoid
  77 </I>&gt;<i>vast amounts of useless text. I assume you have a website, so you can
  78 </I>&gt;<i>use this to display information that you want people to be able to
  79 </I>&gt;<i>&quot;keep&quot;.
  80 </I>
  81 Frankly, logonnews is useless, and most of my users and opers agree.  It
  82 scrolls off too fast.  Ideally, it shoudl have a delay to prevent it being
  83 lost in the system notices on connection.  Maybe a 10 second delay beforee
  84 it flashes by, to give the user time to connect, etc, and then they might
  85 actually SEE it.  Most users I know don't tend to make a habit of readin gth
  86 ebacklog in their status windows when they connect to the network......
  87
  88 Anyhow these were just friendly suggestions, tryign to solve a problem I
  89 have.  I don't plan to simply go &quot;OK well, since one or two others out there
  90 think my ideas are dumb for them, obviously I ought to abandon them, because
  91 they MUST be dumb&quot;  That attitude is ignorant, and I think my suggestions
  92 had weight and merit.  Your objections have merit too, but I see you did not
  93 suggest any useful alternatives or workarounds... Thanks for the input!
  94
  95 &gt;<i>M.
  96 </I>
  97
  98 </PRE>
  99
 100 <!--endarticle-->
 101     <HR>
 102     <P><UL>
 103         <!--threads-->
 104         <LI>Previous message: <A HREF="002126.html">[IRCServices Coding] Mass memos
 105 </A></li>
 106         <LI>Next message: <A HREF="002128.html">[IRCServices Coding] Mass memos
 107 </A></li>
 108          <LI> <B>Messages sorted by:</B>
 109               <a href="date.html#2127">[ date ]</a>
 110               <a href="thread.html#2127">[ thread ]</a>
 111               <a href="subject.html#2127">[ subject ]</a>
 112               <a href="author.html#2127">[ author ]</a>
 113          </LI>
 114        </UL>
 115
 116 </body></html>