software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/002130.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=000e01c361e7%24a9d8c040%246282edc1%40mark2k">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002134.html">
  11    <LINK REL="Next"  HREF="002132.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Mass memos</H1>
  15     <B>Trevor Talbot</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Mass%20memos&In-Reply-To=000e01c361e7%24a9d8c040%246282edc1%40mark2k"
  17        TITLE="[IRCServices Coding] Mass memos">quension at mac.com
  18        </A><BR>
  19     <I>Wed Aug 13 15:30:41 PDT 2003</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002134.html">[IRCServices Coding] Mass memos
  22 </A></li>
  23         <LI>Next message: <A HREF="002132.html">[IRCServices Coding] Mass memos
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2130">[ date ]</a>
  27               <a href="thread.html#2130">[ thread ]</a>
  28               <a href="subject.html#2130">[ subject ]</a>
  29               <a href="author.html#2130">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>On Wednesday, Aug 13, 2003, at 15:10 US/Pacific, M wrote:
  35
  36 &gt;<i> Saturn wrote:
  37 </I>&gt;&gt;<i> This is not spam, and should probably be only accessible by either
  38 </I>&gt;&gt;<i> Services Admins or Services OPs.  The intention is to announce
  39 </I>&gt;&gt;<i> outages, important events, etc
  40 </I>&gt;<i>
  41 </I>&gt;<i> /os global &lt;message&gt;
  42 </I>
  43 That doesn't cover people who aren't online at the time.
  44
  45 &gt;&gt;<i> I did come across that after sending the email to the group.  Sadly,
  46 </I>&gt;&gt;<i> it provides no help whatsoever to the memo question.. but it did shed
  47 </I>&gt;&gt;<i> light on the question i asked.....
  48 </I>&gt;<i>
  49 </I>&gt;<i> You did not ask a memo question that has an answer, you made a feature
  50 </I>&gt;<i> request. The nick prefix has nothing to do with memos.
  51 </I>
  52 He described a visibility problem as a reason for the feature request.
  53 He also described a nick linking issue while attempting to handle a
  54 &quot;mass memo&quot; feature on his own.  While technically not questions, I
  55 would think it was obvious that responses were desired in those
  56 contexts.
  57
  58 &gt;&gt;<i> Frankly, logonnews is useless, and most of my users and opers agree.
  59 </I>&gt;&gt;<i> It scrolls off too fast.  Ideally, it shoudl have a delay to prevent
  60 </I>&gt;&gt;<i> it being lost in the system notices on connection.  Maybe a 10 second
  61 </I>&gt;&gt;<i> delay beforee it flashes by, to give the user time to connect, etc,
  62 </I>&gt;&gt;<i> and then they might actually SEE it.
  63 </I>&gt;<i>
  64 </I>&gt;<i> That is hardly a services issue. The IRCd would be the place to add
  65 </I>&gt;<i> false delays into the login process.
  66 </I>
  67 Logonnews is not part of the ircd's login process.
  68
  69 &gt;&gt;<i> Most users I know don't tend to make a habit of readin gth ebacklog
  70 </I>&gt;&gt;<i> in their status windows when they connect to the network......
  71 </I>&gt;<i>
  72 </I>&gt;<i> Many users do not check memos on a regular basis either so spamming
  73 </I>&gt;<i> via memoserv would just fill their memo box and they are still are not
  74 </I>&gt;<i> guaranteed to be read. They could also add you to their ignore list so
  75 </I>&gt;<i> your message would not get through in any case.
  76 </I>
  77 Memos generally have a much higher visibility than logonnews.  You're
  78 welcome to provide very thorough examples to the contrary, but you'll
  79 be working against the tide of experience from a lot of people on a lot
  80 of different networks, apparently including Saturn.
  81
  82 -- Quension
  83
  84 </PRE>
  85
  86 <!--endarticle-->
  87     <HR>
  88     <P><UL>
  89         <!--threads-->
  90         <LI>Previous message: <A HREF="002134.html">[IRCServices Coding] Mass memos
  91 </A></li>
  92         <LI>Next message: <A HREF="002132.html">[IRCServices Coding] Mass memos
  93 </A></li>
  94          <LI> <B>Messages sorted by:</B>
  95               <a href="date.html#2130">[ date ]</a>
  96               <a href="thread.html#2130">[ thread ]</a>
  97               <a href="subject.html#2130">[ subject ]</a>
  98               <a href="author.html#2130">[ author ]</a>
  99          </LI>
 100        </UL>
 101
 102 </body></html>