software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/002835.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] UnrealIRCd - PREFIX_AQ
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20UnrealIRCd%20-%20PREFIX_AQ&In-Reply-To=000a01c3c0d5%24d941a1b0%240100a8c0%40blauwhome">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002834.html">
  11    <LINK REL="Next"  HREF="002836.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] UnrealIRCd - PREFIX_AQ</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20UnrealIRCd%20-%20PREFIX_AQ&In-Reply-To=000a01c3c0d5%24d941a1b0%240100a8c0%40blauwhome"
  17        TITLE="[IRCServices Coding] UnrealIRCd - PREFIX_AQ">achurch at achurch.org
  18        </A><BR>
  19     <I>Sat Dec 13 02:34:46 PST 2003</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002834.html">[IRCServices Coding] UnrealIRCd - PREFIX_AQ
  22 </A></li>
  23         <LI>Next message: <A HREF="002836.html">[IRCServices Coding] UnrealIRCd - PREFIX_AQ
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2835">[ date ]</a>
  27               <a href="thread.html#2835">[ thread ]</a>
  28               <a href="subject.html#2835">[ subject ]</a>
  29               <a href="author.html#2835">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i>As, some of you, might know, UnrealIRCd has a new option for PREFIX_AQ,
  35 </I>&gt;<i>which gives all Protected users and Channel owners new prefixes. You also
  36 </I>&gt;<i>don't require +o if you have +a/q to perform Channel operations like Kicking
  37 </I>&gt;<i>etc.
  38 </I>&gt;<i>
  39 </I>&gt;<i>I was wondering, how does IRCServices cope with these new prefixes? Is there
  40 </I>&gt;<i>something I drastically need change in the protocol setup.
  41 </I>
  42      I don't know how these prefixes are implemented; assuming they use
  43 ordinary nickname change commands, Services will recognize them, but users
  44 will need to link the prefixed nicknames to their regular nicknames or they
  45 will lose privileges on the channel (which could potentially result in mode
  46 change loops).  I have no plans to add specific support for such prefixes.
  47
  48 &gt;<i>Also, does
  49 </I>&gt;<i>IRCServices still set +ao when a user's got AUTOPROTECT and also +qo when a
  50 </I>&gt;<i>user is the OWNER. Since this is no longer needed in Unreal with the
  51 </I>&gt;<i>PREFIX_AQ enabled, is there a way to stop IRCServices from setting both o
  52 </I>&gt;<i>and q/a when a user has sufficient access.
  53 </I>
  54      No, there isn't.
  55
  56   --Andrew Church
  57     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
  58     <A HREF="http://achurch.org/">http://achurch.org/</A>
  59
  60 </PRE>
  61
  62 <!--endarticle-->
  63     <HR>
  64     <P><UL>
  65         <!--threads-->
  66         <LI>Previous message: <A HREF="002834.html">[IRCServices Coding] UnrealIRCd - PREFIX_AQ
  67 </A></li>
  68         <LI>Next message: <A HREF="002836.html">[IRCServices Coding] UnrealIRCd - PREFIX_AQ
  69 </A></li>
  70          <LI> <B>Messages sorted by:</B>
  71               <a href="date.html#2835">[ date ]</a>
  72               <a href="thread.html#2835">[ thread ]</a>
  73               <a href="subject.html#2835">[ subject ]</a>
  74               <a href="author.html#2835">[ author ]</a>
  75          </LI>
  76        </UL>
  77
  78 </body></html>