software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001685.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Suggestion
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=003301c0b335%2495383020%240200000a%40strider">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001676.html">
  11    <LINK REL="Next"  HREF="001686.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Suggestion</H1>
  15     <B>Mark Hetherington</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=003301c0b335%2495383020%240200000a%40strider"
  17        TITLE="[IRCServices] Suggestion">markh at eurodltd.co.uk
  18        </A><BR>
  19     <I>Fri Mar 23 12:25:01 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001676.html">[IRCServices] Suggestion
  22 </A></li>
  23         <LI>Next message: <A HREF="001686.html">[IRCServices] Suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1685">[ date ]</a>
  27               <a href="thread.html#1685">[ thread ]</a>
  28               <a href="subject.html#1685">[ subject ]</a>
  29               <a href="author.html#1685">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> On our services we added some messages sent via globops. When someone
  35 </I>&gt;<i> registers a channel or a nick, we get a message saying they
  36 </I>&gt;<i> did so. You
  37 </I>&gt;<i> could implement something like this to the suspension. If a
  38 </I>&gt;<i> nick or channel
  39 </I>&gt;<i> becomes suspended due to bad passwords, send a globops, then
  40 </I>&gt;<i> an IRCop can
  41 </I>&gt;<i> deal with it when it happens.
  42 </I>
  43 I would expect a globops would be sent in response to services doing this
  44 since most &quot;decisions&quot; made by services are so announced.
  45
  46 &gt;<i> Also, despite restricting the nickserv nick list, many
  47 </I>&gt;<i> servers list their
  48 </I>&gt;<i> ircops in their motd or website or both. IRCops are a very
  49 </I>&gt;<i> common target in
  50 </I>&gt;<i> IRC war. This very well could be annoying to an ircop to find
  51 </I>&gt;<i> their nick was
  52 </I>&gt;<i> suspended because someone decided they would like to have &quot;fun&quot;.
  53 </I>
  54 It is one of our oper policies that oper nicknames be as secure as possible.
  55 Immediate kill and specific host in the access list etc. So noone could use
  56 an opers name long enough to attempt to chat let alone cause their nickname
  57 to be suspended.
  58
  59 Mark.
  60 CTCP Networks.
  61
  62
  63
  64 </PRE>
  65
  66 <!--endarticle-->
  67     <HR>
  68     <P><UL>
  69         <!--threads-->
  70         <LI>Previous message: <A HREF="001676.html">[IRCServices] Suggestion
  71 </A></li>
  72         <LI>Next message: <A HREF="001686.html">[IRCServices] Suggestion
  73 </A></li>
  74          <LI> <B>Messages sorted by:</B>
  75               <a href="date.html#1685">[ date ]</a>
  76               <a href="thread.html#1685">[ thread ]</a>
  77               <a href="subject.html#1685">[ subject ]</a>
  78               <a href="author.html#1685">[ author ]</a>
  79          </LI>
  80        </UL>
  81
  82 </body></html>