[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2003 / 002128.html

<!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=001e01c361e4%24b60c8f20%246401a8c0%40turby">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="002127.html">
   <LINK REL="Next"  HREF="002129.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices Coding] Mass memos</H1>
    <B>M</B> 
    <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Mass%20memos&In-Reply-To=001e01c361e4%24b60c8f20%246401a8c0%40turby"
       TITLE="[IRCServices Coding] Mass memos">mark at ctcp.net
       </A><BR>
    <I>Wed Aug 13 15:10:10 PDT 2003</I>
    <P><UL>
        <LI>Previous message: <A HREF="002127.html">[IRCServices Coding] Mass memos
</A></li>
        <LI>Next message: <A HREF="002129.html">[IRCServices Coding] Mass memos
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#2128">[ date ]</a>
              <a href="thread.html#2128">[ thread ]</a>
              <a href="subject.html#2128">[ subject ]</a>
              <a href="author.html#2128">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Saturn wrote:
&gt;<i> This is not spam, and should probably be only accessible by 
</I>&gt;<i> either Services Admins or Services OPs.  The intention is to 
</I>&gt;<i> announce outages, important events, etc
</I>
/os global &lt;message&gt;

&gt;<i> I did come across that after sending the email to the group.  
</I>&gt;<i> Sadly, it provides no help whatsoever to the memo question.. 
</I>&gt;<i> but it did shed light on the question i asked.....
</I>
You did not ask a memo question that has an answer, you made a feature
request. The nick prefix has nothing to do with memos. 

&gt;<i> &gt;As an SA you can list links for a nick. A user has no need 
</I>&gt;<i> to determine 
</I>&gt;<i> &gt;links of other users.
</I>&gt;<i> 
</I>&gt;<i> Who decided that? you? Perhaps I would like my users to be 
</I>&gt;<i> able to see the
</I>&gt;<i> links for each other...   
</I>
I assume the developer decided that but I am more than happy for it to
be that way and would request it to be so or avoid the package if it was
not. Users may have linked nicks that they do not want everybody to know
of. Allowing access to any user will mean they just register separate
nicks again which is more work for them and defeats the advantages of
the link system. 

&gt;<i> Frankly, logonnews is useless, and most of my users and opers 
</I>&gt;<i> agree.  It scrolls off too fast.  Ideally, it shoudl have a 
</I>&gt;<i> delay to prevent it being lost in the system notices on 
</I>&gt;<i> connection.  Maybe a 10 second delay beforee it flashes by, 
</I>&gt;<i> to give the user time to connect, etc, and then they might 
</I>&gt;<i> actually SEE it.  
</I>
That is hardly a services issue. The IRCd would be the place to add
false delays into the login process. 

I doubt users would welcome having a connection to the network paused
for such a reason. 

&gt;<i> Most users I know don't tend to make a 
</I>&gt;<i> habit of readin gth ebacklog in their status windows when 
</I>&gt;<i> they connect to the network......
</I>
Many users do not check memos on a regular basis either so spamming via
memoserv would just fill their memo box and they are still are not
guaranteed to be read. They could also add you to their ignore list so
your message would not get through in any case. 

&gt;<i> Anyhow these were just friendly suggestions, tryign to solve 
</I>&gt;<i> a problem I have.  I don't plan to simply go &quot;OK well, since 
</I>&gt;<i> one or two others out there think my ideas are dumb for them, 
</I>&gt;<i> obviously I ought to abandon them, because they MUST be dumb&quot; 
</I>&gt;<i>  That attitude is ignorant, and I think my suggestions had 
</I>&gt;<i> weight and merit.  Your objections have merit too, but I see 
</I>&gt;<i> you did not suggest any useful alternatives or workarounds...
</I>
You stated in your original message that there were alternative services
packages that provide this. You also said you would not consider using
logonnews. Pointing out the obvious seemed a pointless exercise. 

As suggested above, &quot;mass memos&quot; would not solve your &quot;problem&quot;.
 
M.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (<A HREF="http://www.grisoft.com">http://www.grisoft.com</A>).
Version: 6.0.507 / Virus Database: 304 - Release Date: 04/08/2003
 

</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="002127.html">[IRCServices Coding] Mass memos
</A></li>
	<LI>Next message: <A HREF="002129.html">[IRCServices Coding] Mass memos
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#2128">[ date ]</a>
              <a href="thread.html#2128">[ thread ]</a>
              <a href="subject.html#2128">[ subject ]</a>
              <a href="author.html#2128">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	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=001e01c361e4%24b60c8f20%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="002127.html">
	11	<LINK REL="Next" HREF="002129.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=001e01c361e4%24b60c8f20%246401a8c0%40turby"
	17	TITLE="[IRCServices Coding] Mass memos">mark at ctcp.net
	18	</A><BR>
	19	<I>Wed Aug 13 15:10:10 PDT 2003</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="002127.html">[IRCServices Coding] Mass memos
	22	</A></li>
	23	<LI>Next message: <A HREF="002129.html">[IRCServices Coding] Mass memos
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#2128">[ date ]</a>
	27	<a href="thread.html#2128">[ thread ]</a>
	28	<a href="subject.html#2128">[ subject ]</a>
	29	<a href="author.html#2128">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>Saturn wrote:
	35	><i> This is not spam, and should probably be only accessible by
	36	</I>><i> either Services Admins or Services OPs. The intention is to
	37	</I>><i> announce outages, important events, etc
	38	</I>
	39	/os global <message>
	40
	41	><i> I did come across that after sending the email to the group.
	42	</I>><i> Sadly, it provides no help whatsoever to the memo question..
	43	</I>><i> but it did shed light on the question i asked.....
	44	</I>
	45	You did not ask a memo question that has an answer, you made a feature
	46	request. The nick prefix has nothing to do with memos.
	47
	48	><i> >As an SA you can list links for a nick. A user has no need
	49	</I>><i> to determine
	50	</I>><i> >links of other users.
	51	</I>><i>
	52	</I>><i> Who decided that? you? Perhaps I would like my users to be
	53	</I>><i> able to see the
	54	</I>><i> links for each other...
	55	</I>
	56	I assume the developer decided that but I am more than happy for it to
	57	be that way and would request it to be so or avoid the package if it was
	58	not. Users may have linked nicks that they do not want everybody to know
	59	of. Allowing access to any user will mean they just register separate
	60	nicks again which is more work for them and defeats the advantages of
	61	the link system.
	62
	63	><i> Frankly, logonnews is useless, and most of my users and opers
	64	</I>><i> agree. It scrolls off too fast. Ideally, it shoudl have a
65	</I>><i> delay to prevent it being lost in the system notices on
66	</I>><i> connection. Maybe a 10 second delay beforee it flashes by,
67	</I>><i> to give the user time to connect, etc, and then they might
68	</I>><i> actually SEE it.
69	</I>
70	That is hardly a services issue. The IRCd would be the place to add
71	false delays into the login process.
72
73	I doubt users would welcome having a connection to the network paused
74	for such a reason.
75
76	><i> Most users I know don't tend to make a
77	</I>><i> habit of readin gth ebacklog in their status windows when
78	</I>><i> they connect to the network......
79	</I>
80	Many users do not check memos on a regular basis either so spamming via
81	memoserv would just fill their memo box and they are still are not
82	guaranteed to be read. They could also add you to their ignore list so
83	your message would not get through in any case.
84
85	><i> Anyhow these were just friendly suggestions, tryign to solve
86	</I>><i> a problem I have. I don't plan to simply go "OK well, since
87	</I>><i> one or two others out there think my ideas are dumb for them,
88	</I>><i> obviously I ought to abandon them, because they MUST be dumb"
89	</I>><i> That attitude is ignorant, and I think my suggestions had
90	</I>><i> weight and merit. Your objections have merit too, but I see
91	</I>><i> you did not suggest any useful alternatives or workarounds...
92	</I>
93	You stated in your original message that there were alternative services
94	packages that provide this. You also said you would not consider using
95	logonnews. Pointing out the obvious seemed a pointless exercise.
96
97	As suggested above, "mass memos" would not solve your "problem".
98
99	M.
100
101	---
102	Outgoing mail is certified Virus Free.
103	Checked by AVG anti-virus system (<A HREF="http://www.grisoft.com">http://www.grisoft.com</A>).
104	Version: 6.0.507 / Virus Database: 304 - Release Date: 04/08/2003
105
106
107	</PRE>
108
109	<!--endarticle-->
110	<HR>
111	<P><UL>
112	<!--threads-->
113	<LI>Previous message: <A HREF="002127.html">[IRCServices Coding] Mass memos
114	</A></li>
115	<LI>Next message: <A HREF="002129.html">[IRCServices Coding] Mass memos
116	</A></li>
117	<LI> <B>Messages sorted by:</B>
118	<a href="date.html#2128">[ date ]</a>
119	<a href="thread.html#2128">[ thread ]</a>
120	<a href="subject.html#2128">[ subject ]</a>
121	<a href="author.html#2128">[ author ]</a>
122	</LI>
123	</UL>
124
125	</body></html>