software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/002134.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=003501c361ed%246759fd00%246401a8c0%40turby">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002133.html">
  11    <LINK REL="Next"  HREF="002130.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Mass memos</H1>
  15     <B>M</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Mass%20memos&In-Reply-To=003501c361ed%246759fd00%246401a8c0%40turby"
  17        TITLE="[IRCServices Coding] Mass memos">mark at ctcp.net
  18        </A><BR>
  19     <I>Wed Aug 13 16:21:57 PDT 2003</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002133.html">[IRCServices Coding] Mass memos
  22 </A></li>
  23         <LI>Next message: <A HREF="002130.html">[IRCServices Coding] Mass memos
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2134">[ date ]</a>
  27               <a href="thread.html#2134">[ thread ]</a>
  28               <a href="subject.html#2134">[ subject ]</a>
  29               <a href="author.html#2134">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Saturn wrote:
  35 &gt;<i> As to the mass memo function, I did request it as a feature,
  36 </I>&gt;<i> but also implied that I would like a suggestion for solutions
  37 </I>&gt;<i> to my problem... telling me all the reasons why it is no so,
  38 </I>&gt;<i> is no help to ANYONE....
  39 </I>
  40 Is every response to a post required to address every single one of a
  41 the posted questions or suggestions? That is not the nature of a mailing
  42 list. Members are free to respond to all/some/none of a post.
  43
  44 Discussion, particularly for new features has to include all aspects
  45 whether or not they agree with you.
  46
  47 &gt;<i> As to the delay, you misunderstand me (but apparently at
  48 </I>&gt;<i> least 2 other people got it on the first blush):  I mean have
  49 </I>&gt;<i> services delay displaying the logonnews for 10 seconds (or
  50 </I>&gt;<i> maybe delay defined in the config);  The whole point is to
  51 </I>&gt;<i> allow the user to be fully logged in, join a channel, etc,
  52 </I>&gt;<i> before the news is displayed to them, so that they will
  53 </I>&gt;<i> actually NOTICE it.
  54 </I>
  55 You are assuming that people will switch back to their status window
  56 after having joined channels and started chatting in them. This IME does
  57 not happen at the moment so why would a delay make it happen.
  58
  59 &gt;<i> The global message works just fine, yes, however, if you stop
  60 </I>&gt;<i> to think about it, it does NOT notify every user, rather only
  61 </I>&gt;<i> those that happen to be online RIGHT NOW.  What about the 3/4
  62 </I>&gt;<i> to 4/5 of my users who just happen to be at work, asleep in
  63 </I>&gt;<i> another time zone, or simply offline today?  Shall I global
  64 </I>&gt;<i> message every 30 minutes for 24 hours perhaps?  sheesh
  65 </I>
  66 Did I suggest that? No.
  67
  68 If you have outages which take a long time to correct, then I suggest
  69 that is the problem to address. A services upgrade (with the 5.0 series)
  70 can be done within seconds with no impact on online users and no need to
  71 spam every user of the network to warn of it. An /os global in such a
  72 case is merely polite.
  73
  74 Outages generally only affect online users, so /os global is a useful
  75 way to let them know of an upcoming outage. Pre planning every outage is
  76 not feasible IRL. What if you plan a particular outage, then have to
  77 cancel and replan. Three memos - one for first plan, second to cancel,
  78 third to rebook. Similar for an outage that does not achieve the desired
  79 effect.
  80
  81 As with logon news, users can choose to read their memos or not. If they
  82 choose not to or to ignore messages from you, you do not achieve the
  83 effect you desire. Logon news is not optional. Memos are.
  84
  85 There are various options available to you with current systems. A
  86 mailing list in conjunction with the web site would be far better and
  87 would be opt in. Any system which a user has to opt out of or in this
  88 case has no option to and must ignore the user (in this case you and any
  89 other mass memo senders) is spam.
  90
  91 &gt;<i> As for those unregistered users not getting the news:  On my
  92 </I>&gt;<i> network, they are unregistered, and therefore can go get the
  93 </I>&gt;<i> news off the website or by asking around.  News is for
  94 </I>&gt;<i> regulars, and regulars register their nicks.
  95 </I>
  96 A user who does not have a registered nick, is not necessarily someone
  97 who has chosen not to register. It may be a new user (to the network or
  98 to IRC). In this case, the server they just joined (or maybe services)
  99 is about to go to outage and their lack of registration means they are
 100 unaware of it from mass memo so just go elsewhere.
 101
 102 Personally I do not discriminate against unregistered users.
 103 Registration provides more features but is not a requirement.
 104
 105 It looks like you are requesting an &quot;on /ns identify news&quot; rather than
 106 logon news. This is somewhat simpler to implement but a different
 107 request. It does not remove the requirement for logon news for all users
 108 whether new users that are not yet registered or registered users on an
 109 auto connect that have not identified.
 110
 111 &gt;<i> If you want to be 100% equal to all users, then why not
 112 </I>&gt;<i> simply not run services in the first place?  The whole point
 113 </I>&gt;<i> is that everyone registers. Those that don't, do so of their
 114 </I>&gt;<i> own choice, and I think most users know what they're giving up.
 115 </I>
 116 Not at all. It is a service provided for the users that they can choose
 117 to use or not use.
 118
 119 &gt;<i> And for the record, mass memos as I've been forced to do them
 120 </I>&gt;<i> thus far, have been met with good reviews and do, in fact,
 121 </I>&gt;<i> solve my problem.  The only hitch is that people with linked
 122 </I>&gt;<i> nicks end up with multiple copies, and I would appreciate an
 123 </I>&gt;<i> easier way to a) send a memo to all users, and b) avoid users
 124 </I>&gt;<i> receiving multiple copies if they have linked nicks.  Is this
 125 </I>&gt;<i> really so much to ask for?
 126 </I>
 127 I have stated my opinions on this in previous posts and this one.
 128
 129 &gt;<i> Your condescending attitude is certainly not appreciated, and
 130 </I>
 131 LOL. Glass houses.
 132
 133 &gt;<i> I will be ignoring any future posts you make to this
 134 </I>&gt;<i> discussion group, but will be eagerly reading any other
 135 </I>&gt;<i> suggestions anyone else does post.
 136 </I>
 137 Should I care?
 138
 139 Would you care to share publicly how inaccurate the above statement you
 140 made was?
 141
 142 &gt;<i> Thanks to Trevor and Russell for the support on my
 143 </I>&gt;<i> suggestions -- at least I know the friendly folks in the
 144 </I>&gt;<i> group can understand what I meant...
 145 </I>
 146 Interesting POV.
 147
 148 M.
 149
 150 ---
 151 Outgoing mail is certified Virus Free.
 152 Checked by AVG anti-virus system (<A HREF="http://www.grisoft.com">http://www.grisoft.com</A>).
 153 Version: 6.0.507 / Virus Database: 304 - Release Date: 04/08/2003
 154
 155
 156 </PRE>
 157
 158 <!--endarticle-->
 159     <HR>
 160     <P><UL>
 161         <!--threads-->
 162         <LI>Previous message: <A HREF="002133.html">[IRCServices Coding] Mass memos
 163 </A></li>
 164         <LI>Next message: <A HREF="002130.html">[IRCServices Coding] Mass memos
 165 </A></li>
 166          <LI> <B>Messages sorted by:</B>
 167               <a href="date.html#2134">[ date ]</a>
 168               <a href="thread.html#2134">[ thread ]</a>
 169               <a href="subject.html#2134">[ subject ]</a>
 170               <a href="author.html#2134">[ author ]</a>
 171          </LI>
 172        </UL>
 173
 174 </body></html>