software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2003/003966.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] -Global- From Craig: ?
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20-Global-%20From%20Craig%3A%20%3F&In-Reply-To=20030714001640.XYCS14037.mta5-svc.business.ntl.com%40i-br0ked-it">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="003962.html">
  11    <LINK REL="Next"  HREF="003967.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] -Global- From Craig: ?</H1>
  15     <B>M</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20-Global-%20From%20Craig%3A%20%3F&In-Reply-To=20030714001640.XYCS14037.mta5-svc.business.ntl.com%40i-br0ked-it"
  17        TITLE="[IRCServices] -Global- From Craig: ?">mark at ctcp.net
  18        </A><BR>
  19     <I>Mon Jul 14 14:53:55 PDT 2003</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003962.html">[IRCServices] -Global- From Craig: ?
  22 </A></li>
  23         <LI>Next message: <A HREF="003967.html">[IRCServices] -Global- From Craig: ?
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#3966">[ date ]</a>
  27               <a href="thread.html#3966">[ thread ]</a>
  28               <a href="subject.html#3966">[ subject ]</a>
  29               <a href="author.html#3966">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> i dunno about anyone else, but i've often gotten complaints
  35 </I>&gt;<i> that were sent about globals on my network from users..
  36 </I>&gt;<i> Globals which other members of staff and have nothing to do with me.
  37 </I>
  38 I disagree. Sometimes you might not wish to attribute the message to a
  39 single individual. If globals are being issued that need sufficient
  40 support to make this suggestion, then surely it is a problem that needs
  41 resolving within your Admins/Opers rather than a coding one. I assume
  42 that you have a central channel for network support and that appropriate
  43 individuals are rquired to be in that channel, so that would surely be
  44 the first place where users would go for assistance and the person who
  45 issued it would be present.
  46
  47 The name of the person issuing it is logged so can be tracked. IMO a
  48 better suggestion would be to add a wallops to services stating that a
  49 given nick issued a global since this would at least inform opers (and
  50 +w users) who issued a given global. I did think this functionality
  51 existed, but a quick look at the code does not suggest it does and a
  52 quick test does not produce a wallops.
  53
  54 M.
  55
  56 </PRE>
  57
  58 <!--endarticle-->
  59     <HR>
  60     <P><UL>
  61         <!--threads-->
  62         <LI>Previous message: <A HREF="003962.html">[IRCServices] -Global- From Craig: ?
  63 </A></li>
  64         <LI>Next message: <A HREF="003967.html">[IRCServices] -Global- From Craig: ?
  65 </A></li>
  66          <LI> <B>Messages sorted by:</B>
  67               <a href="date.html#3966">[ date ]</a>
  68               <a href="thread.html#3966">[ thread ]</a>
  69               <a href="subject.html#3966">[ subject ]</a>
  70               <a href="author.html#3966">[ author ]</a>
  71          </LI>
  72        </UL>
  73
  74 </body></html>