[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 000254.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices Coding] Making Services 5 friendly external pseudo clients
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Making%20Services%205%20friendly%20external%20pseudo%20clients&In-Reply-To=3c668666.26076%40achurch.org">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="000253.html">
   <LINK REL="Next"  HREF="000257.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices Coding] Making Services 5 friendly external pseudo clients</H1>
    <B>Mark Hetherington</B> 
    <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Making%20Services%205%20friendly%20external%20pseudo%20clients&In-Reply-To=3c668666.26076%40achurch.org"
       TITLE="[IRCServices Coding] Making Services 5 friendly external pseudo clients">mark at mhetherington.demon.co.uk
       </A><BR>
    <I>Sun Feb 10 08:51:04 PST 2002</I>
    <P><UL>
        <LI>Previous message: <A HREF="000253.html">[IRCServices Coding] Services 5 - AKILL expiry
</A></li>
        <LI>Next message: <A HREF="000257.html">[IRCServices Coding] SMTP debug
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#254">[ date ]</a>
              <a href="thread.html#254">[ thread ]</a>
              <a href="subject.html#254">[ subject ]</a>
              <a href="author.html#254">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Currently on our network we have a couple of psuedo clients which are not
part of IRC Services but have similar &quot;powers&quot; as +S psudeo clients on
ulined servers. This includes a StatServ client that we had been running for
some time prior to the first StatServ appearing in IRC Services and an open
proxy monitor.

Although they generally live happily together, since Services does not
recognise these external psuedo clients, occasionally they tend to &quot;fight&quot;.

Using our StatServ as an example, this basically sits in a channel
announcing various information about the network for the use of IRCops.
Ideally we would like this channel locked to be an oper only channel but
currently have to rely on an eggdrop bot to enforce this rather than
ChanServ.

The problems are twofold. Firstly, since Services has no way of recognising
an external psuedo client, when StatServ ops itself, Chanserv will
immediately deop it. Secondly, if the channel mode is set to mode +O,
StatServ can happily join the channel (as a +S user), but services will
enforce the mode and kick StatServ as a non-oper. This results in a vicious
flood of join/kicks as they both fight for their rights :)

Hopefully, the built-in StatServ will eventually provide most if not all of
the functionality of our existing StatServ and anything it doesn't provide
we can develop into a custom module of services. But, until that time, we
need to maintain StatServ as an external pseudo client.

The simplest way seems to be some recognition within services for other
ulined servers possibly by detecting the +S user mode in a similar way that
our StatServ will recognise each Services pseudo client as such. Is there
anything in current versions of services that would allow the two servers to
live together or anything we could set in our external pseudo clients which
would cause services to ignore their actions?


Mark.


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000253.html">[IRCServices Coding] Services 5 - AKILL expiry
</A></li>
	<LI>Next message: <A HREF="000257.html">[IRCServices Coding] SMTP debug
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#254">[ date ]</a>
              <a href="thread.html#254">[ thread ]</a>
              <a href="subject.html#254">[ subject ]</a>
              <a href="author.html#254">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices Coding] Making Services 5 friendly external pseudo clients
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Making%20Services%205%20friendly%20external%20pseudo%20clients&In-Reply-To=3c668666.26076%40achurch.org">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="000253.html">
	11	<LINK REL="Next" HREF="000257.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices Coding] Making Services 5 friendly external pseudo clients</H1>
	15	<B>Mark Hetherington</B>
	16	<A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Making%20Services%205%20friendly%20external%20pseudo%20clients&In-Reply-To=3c668666.26076%40achurch.org"
	17	TITLE="[IRCServices Coding] Making Services 5 friendly external pseudo clients">mark at mhetherington.demon.co.uk
	18	</A><BR>
	19	<I>Sun Feb 10 08:51:04 PST 2002</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="000253.html">[IRCServices Coding] Services 5 - AKILL expiry
	22	</A></li>
	23	<LI>Next message: <A HREF="000257.html">[IRCServices Coding] SMTP debug
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#254">[ date ]</a>
	27	<a href="thread.html#254">[ thread ]</a>
	28	<a href="subject.html#254">[ subject ]</a>
	29	<a href="author.html#254">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>Currently on our network we have a couple of psuedo clients which are not
	35	part of IRC Services but have similar "powers" as +S psudeo clients on
	36	ulined servers. This includes a StatServ client that we had been running for
	37	some time prior to the first StatServ appearing in IRC Services and an open
	38	proxy monitor.
	39
	40	Although they generally live happily together, since Services does not
	41	recognise these external psuedo clients, occasionally they tend to "fight".
	42
	43	Using our StatServ as an example, this basically sits in a channel
	44	announcing various information about the network for the use of IRCops.
	45	Ideally we would like this channel locked to be an oper only channel but
	46	currently have to rely on an eggdrop bot to enforce this rather than
	47	ChanServ.
	48
	49	The problems are twofold. Firstly, since Services has no way of recognising
	50	an external psuedo client, when StatServ ops itself, Chanserv will
	51	immediately deop it. Secondly, if the channel mode is set to mode +O,
	52	StatServ can happily join the channel (as a +S user), but services will
	53	enforce the mode and kick StatServ as a non-oper. This results in a vicious
	54	flood of join/kicks as they both fight for their rights :)
	55
	56	Hopefully, the built-in StatServ will eventually provide most if not all of
	57	the functionality of our existing StatServ and anything it doesn't provide
	58	we can develop into a custom module of services. But, until that time, we
	59	need to maintain StatServ as an external pseudo client.
	60
	61	The simplest way seems to be some recognition within services for other
	62	ulined servers possibly by detecting the +S user mode in a similar way that
	63	our StatServ will recognise each Services pseudo client as such. Is there
	64	anything in current versions of services that would allow the two servers to
65	live together or anything we could set in our external pseudo clients which
66	would cause services to ignore their actions?
67
68
69	Mark.
70
71
72	</PRE>
73
74	<!--endarticle-->
75	<HR>
76	<P><UL>
77	<!--threads-->
78	<LI>Previous message: <A HREF="000253.html">[IRCServices Coding] Services 5 - AKILL expiry
79	</A></li>
80	<LI>Next message: <A HREF="000257.html">[IRCServices Coding] SMTP debug
81	</A></li>
82	<LI> <B>Messages sorted by:</B>
83	<a href="date.html#254">[ date ]</a>
84	<a href="thread.html#254">[ thread ]</a>
85	<a href="subject.html#254">[ subject ]</a>
86	<a href="author.html#254">[ author ]</a>
87	</LI>
88	</UL>
89
90	</body></html>