software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/002836.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=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002835.html">
  11    <LINK REL="Next"  HREF="002837.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] UnrealIRCd - PREFIX_AQ</H1>
  15     <B>FreakyComputer</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20UnrealIRCd%20-%20PREFIX_AQ&In-Reply-To="
  17        TITLE="[IRCServices Coding] UnrealIRCd - PREFIX_AQ">freakycomputer at global.co.za
  18        </A><BR>
  19     <I>Sat Dec 13 07:38:24 PST 2003</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002835.html">[IRCServices Coding] UnrealIRCd - PREFIX_AQ
  22 </A></li>
  23         <LI>Next message: <A HREF="002837.html">[IRCServices Coding] feature request: instant messanger fields
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2836">[ date ]</a>
  27               <a href="thread.html#2836">[ thread ]</a>
  28               <a href="subject.html#2836">[ subject ]</a>
  29               <a href="author.html#2836">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Actually, all it is, is that people with chumode +a and +q just get a symbol
  35 in front of their nicks in the channel, ~ to owners and &amp; protected users
  36 (just like @ is to ops and % is to halfops). The thing about only receiving
  37 the +q/a without the +o isn't a major thing, and there was just little
  38 changes made to the unreal protocol (new_chanusermodes) to accomodate the
  39 change of prefixes/symbol. But there is another thing I found. There isn't a
  40 way for the founder/owner to set him/herself -q in the channel. We have
  41 tried several things, such as with and without the new prefixes, with or
  42 without identifying, everything. I would think the services would set -q
  43 when the user issues a DEPROTECT command, but the services just say that the
  44 user is already not a protected user, so if there can be a fix to that
  45 command, or perhaps a new command: FOUNDER, DEFOUNDER, it might make it
  46 easier for channels where some rule of &quot;deopping yourself while offduty&quot;
  47 applies.
  48
  49 Thanks for the prompt replies thusfar :D
  50 FC
  51
  52 ----- Original Message -----
  53 From: &quot;Andrew Church&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>&gt;
  54 To: &quot;serv-coding&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>&gt;
  55 Sent: Friday, December 12, 2003 7:34 PM
  56 Subject: Re: [IRCServices Coding] UnrealIRCd - PREFIX_AQ
  57
  58
  59 &gt;<i> &gt;As, some of you, might know, UnrealIRCd has a new option for PREFIX_AQ,
  60 </I>&gt;<i> &gt;which gives all Protected users and Channel owners new prefixes. You also
  61 </I>&gt;<i> &gt;don't require +o if you have +a/q to perform Channel operations like
  62 </I>Kicking
  63 &gt;<i> &gt;etc.
  64 </I>&gt;<i> &gt;
  65 </I>&gt;<i> &gt;I was wondering, how does IRCServices cope with these new prefixes? Is
  66 </I>there
  67 &gt;<i> &gt;something I drastically need change in the protocol setup.
  68 </I>&gt;<i>
  69 </I>&gt;<i>      I don't know how these prefixes are implemented; assuming they use
  70 </I>&gt;<i> ordinary nickname change commands, Services will recognize them, but users
  71 </I>&gt;<i> will need to link the prefixed nicknames to their regular nicknames or
  72 </I>they
  73 &gt;<i> will lose privileges on the channel (which could potentially result in
  74 </I>mode
  75 &gt;<i> change loops).  I have no plans to add specific support for such prefixes.
  76 </I>&gt;<i>
  77 </I>&gt;<i> &gt;Also, does
  78 </I>&gt;<i> &gt;IRCServices still set +ao when a user's got AUTOPROTECT and also +qo when
  79 </I>a
  80 &gt;<i> &gt;user is the OWNER. Since this is no longer needed in Unreal with the
  81 </I>&gt;<i> &gt;PREFIX_AQ enabled, is there a way to stop IRCServices from setting both o
  82 </I>&gt;<i> &gt;and q/a when a user has sufficient access.
  83 </I>&gt;<i>
  84 </I>&gt;<i>      No, there isn't.
  85 </I>&gt;<i>
  86 </I>&gt;<i>   --Andrew Church
  87 </I>&gt;<i>     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
  88 </I>&gt;<i>     <A HREF="http://achurch.org/">http://achurch.org/</A>
  89 </I>&gt;<i> ------------------------------------------------------------------
  90 </I>&gt;<i> To unsubscribe or change your subscription options, visit:
  91 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
  92 </I>&gt;<i>
  93 </I>
  94
  95 </PRE>
  96
  97 <!--endarticle-->
  98     <HR>
  99     <P><UL>
 100         <!--threads-->
 101         <LI>Previous message: <A HREF="002835.html">[IRCServices Coding] UnrealIRCd - PREFIX_AQ
 102 </A></li>
 103         <LI>Next message: <A HREF="002837.html">[IRCServices Coding] feature request: instant messanger fields
 104 </A></li>
 105          <LI> <B>Messages sorted by:</B>
 106               <a href="date.html#2836">[ date ]</a>
 107               <a href="thread.html#2836">[ thread ]</a>
 108               <a href="subject.html#2836">[ subject ]</a>
 109               <a href="author.html#2836">[ author ]</a>
 110          </LI>
 111        </UL>
 112
 113 </body></html>