]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2004/004684.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2004 / 004684.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Clarification with unreal.c
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Clarification%20with%20unreal.c&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="004683.html">
11 <LINK REL="Next" HREF="004685.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Clarification with unreal.c</H1>
15 <B>DeadNotBuried</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Clarification%20with%20unreal.c&In-Reply-To="
17 TITLE="[IRCServices] Clarification with unreal.c">dnb at majestic-liaisons.com
18 </A><BR>
19 <I>Fri Oct 22 01:10:12 PDT 2004</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="004683.html">[IRCServices] Clarification with unreal.c
22 </A></li>
23 <LI>Next message: <A HREF="004685.html">[IRCServices] Clarification with unreal.c
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#4684">[ date ]</a>
27 <a href="thread.html#4684">[ thread ]</a>
28 <a href="subject.html#4684">[ subject ]</a>
29 <a href="author.html#4684">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>
35 if you change the line as stated you will break support in services for the
36 channel owner flag. as services connects to a server it talks to the ircd as
37 a server not as a client, and the unreal 3.2 protocol uses * as a chan owner
38 flag between SERVERS, and &amp; IF compiled to support the new flags for
39 CLIENTS, or just the old @ IF NOT compiled for the new flags for CLIENTS..
40 it's not recommened to change any of those types of flags in services
41 packages, or even IRCd's themselves unless you know how the protocol works.
42
43 DNB
44
45 &gt;<i> OK, I'll start this off by saying that I know nothing about
46 </I>&gt;<i> C programming...
47 </I>&gt;<i>
48 </I>&gt;<i> Anyway, I was feeling bored, so I was reading over unreal.c
49 </I>&gt;<i> and I noticed this in the &quot;new channel user modes&quot; section:
50 </I>&gt;<i>
51 </I>&gt;<i> {'h', {0x00000004,1,1,'%'}}, /* Half-op */
52 </I>&gt;<i>
53 </I>&gt;<i> Now, I'm probably horribly wrong, but the &quot;%&quot; probably
54 </I>&gt;<i> denotes the user prefix (since halfop's nicks are prefixed
55 </I>&gt;<i> with a %).
56 </I>&gt;<i>
57 </I>&gt;<i> If I'm right, then take a look at the next two lines:
58 </I>&gt;<i>
59 </I>&gt;<i> {'a', {0x00000008,1,1,'~'}},
60 </I>&gt;<i> {'q', {0x00000010,1,1,'*',MI_CHANOWNER}},
61 </I>&gt;<i>
62 </I>&gt;<i> Assuming that my above premise is correct, this code
63 </I>&gt;<i> wouldn't be correct, as +a gets the &amp; prefix and +q the ~
64 </I>&gt;<i> prefix in UnrealIRCd. I haven't yet tried changing this
65 </I>&gt;<i> code to see what happens; I'll give that a go this evening.
66 </I>&gt;<i>
67 </I>&gt;<i> Of course, I could be horribly, horribly wrong... if I am,
68 </I>&gt;<i> would someone mind correcting me on this?
69 </I>&gt;<i>
70 </I>
71
72
73 </PRE>
74
75 <!--endarticle-->
76 <HR>
77 <P><UL>
78 <!--threads-->
79 <LI>Previous message: <A HREF="004683.html">[IRCServices] Clarification with unreal.c
80 </A></li>
81 <LI>Next message: <A HREF="004685.html">[IRCServices] Clarification with unreal.c
82 </A></li>
83 <LI> <B>Messages sorted by:</B>
84 <a href="date.html#4684">[ date ]</a>
85 <a href="thread.html#4684">[ thread ]</a>
86 <a href="subject.html#4684">[ subject ]</a>
87 <a href="author.html#4684">[ author ]</a>
88 </LI>
89 </UL>
90
91 </body></html>