software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001677.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=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001671.html">
  11    <LINK REL="Next"  HREF="001678.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Suggestion</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To="
  17        TITLE="[IRCServices] Suggestion">achurch at achurch.org
  18        </A><BR>
  19     <I>Fri Mar 23 03:47:01 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001671.html">[IRCServices] (possible bug?) Report - User can't /identify
  22 </A></li>
  23         <LI>Next message: <A HREF="001678.html">[IRCServices] Suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1677">[ date ]</a>
  27               <a href="thread.html#1677">[ thread ]</a>
  28               <a href="subject.html#1677">[ subject ]</a>
  29               <a href="author.html#1677">[ 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 did so. You
  36 </I>&gt;<i>could implement something like this to the suspension. If a nick or channel
  37 </I>&gt;<i>becomes suspended due to bad passwords, send a globops, then an IRCop can
  38 </I>&gt;<i>deal with it when it happens.
  39 </I>
  40      In Services 4.5.9, you can set limits on the number of bad passwords
  41 per nick before either sending out a warning or suspending the nick (or
  42 both).
  43
  44 &gt;<i>Now I have a suggestion for operserv. Allow ircop level access to operserv
  45 </I>&gt;<i>to anyone with their oline activated.
  46 </I>
  47      This is how OperServ has always worked.  You don't have to have a
  48 registered nick, much less be on any list, to use basic OperServ functions.
  49
  50   --Andrew Church
  51     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | New address - please note.
  52     <A HREF="http://achurch.org/">http://achurch.org/</A> | &#12513;&#12540;&#12523;&#12450;&#12489;&#12524;&#12473;&#12364;&#22793;&#12431;&#12426;&#12414;&#12375;&#12383;&#12290;
  53
  54
  55 </PRE>
  56
  57 <!--endarticle-->
  58     <HR>
  59     <P><UL>
  60         <!--threads-->
  61         <LI>Previous message: <A HREF="001671.html">[IRCServices] (possible bug?) Report - User can't /identify
  62 </A></li>
  63         <LI>Next message: <A HREF="001678.html">[IRCServices] Suggestion
  64 </A></li>
  65          <LI> <B>Messages sorted by:</B>
  66               <a href="date.html#1677">[ date ]</a>
  67               <a href="thread.html#1677">[ thread ]</a>
  68               <a href="subject.html#1677">[ subject ]</a>
  69               <a href="author.html#1677">[ author ]</a>
  70          </LI>
  71        </UL>
  72
  73 </body></html>