software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001223.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Sqline affair
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Sqline%20affair&In-Reply-To=3D52309E.000003.01204%40anar">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001221.html">
  11    <LINK REL="Next"  HREF="001227.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Sqline affair</H1>
  15     <B>Ekim Engin</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Sqline%20affair&In-Reply-To=3D52309E.000003.01204%40anar"
  17        TITLE="[IRCServices Coding] Sqline affair">eengin at talesoft.de
  18        </A><BR>
  19     <I>Thu Aug  8 03:13:27 PDT 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001221.html">AW: [IRCServices Coding] Suggestion - Logonnews
  22 </A></li>
  23         <LI>Next message: <A HREF="001227.html">[IRCServices Coding] Sqline affair
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1223">[ date ]</a>
  27               <a href="thread.html#1223">[ thread ]</a>
  28               <a href="subject.html#1223">[ subject ]</a>
  29               <a href="author.html#1223">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Hi all,
  35
  36 I thought of the sqline feature as an addition (or simplification) of
  37 chardconfed Q-Lines. Now ist intersting that in services5 this behavior
  38 is like another way to forbid. Just wanted to know if it is possible to
  39 make this behavior optional. Like a &quot;SqlineForceNickChange&quot; statement in
  40 the .conf..
  41 Ist usual (on my networks) to sqline e.g. oper nicks to prevent theri
  42 usage, but allow opers to change to them without getting renamed (or
  43 dissalowed) just with a wallops...
  44
  45 Greets Ekim
  46
  47 +------------------------+------------------------+
  48 |<i> Talesin aka Ekim Engin | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">eengin at talesoft.de</A>     |
  49 </I>|<i>   TR-IRCd Coding Team  | <A HREF="http://www.tr-ircd.net">http://www.tr-ircd.net</A> |
  50 </I>|<i>------------------------^------------------------|
  51 </I>|<i>   &lt; Chat begins as it ends - without reason &gt;   |
  52 </I>+-------------------------------------------------+
  53
  54
  55 </PRE>
  56
  57 <!--endarticle-->
  58     <HR>
  59     <P><UL>
  60         <!--threads-->
  61         <LI>Previous message: <A HREF="001221.html">AW: [IRCServices Coding] Suggestion - Logonnews
  62 </A></li>
  63         <LI>Next message: <A HREF="001227.html">[IRCServices Coding] Sqline affair
  64 </A></li>
  65          <LI> <B>Messages sorted by:</B>
  66               <a href="date.html#1223">[ date ]</a>
  67               <a href="thread.html#1223">[ thread ]</a>
  68               <a href="subject.html#1223">[ subject ]</a>
  69               <a href="author.html#1223">[ author ]</a>
  70          </LI>
  71        </UL>
  72
  73 </body></html>