1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] Services in channel opers
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20in%20channel%20opers&In-Reply-To=3E9CAEF5.5070902%40esper.net">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"003774.html">
11 <LINK REL=
"Next" HREF=
"003742.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Services in channel opers
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20in%20channel%20opers&In-Reply-To=3E9CAEF5.5070902%40esper.net"
17 TITLE=
"[IRCServices] Services in channel opers">quension at mac.com
19 <I>Tue Apr
15 20:
50:
42 PDT
2003</I>
21 <LI>Previous message:
<A HREF=
"003774.html">[IRCServices] Services in channel opers
23 <LI>Next message:
<A HREF=
"003742.html">[IRCServices] Services
5.0.16 and
4.5.45 released
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#3776">[ date ]
</a>
27 <a href=
"thread.html#3776">[ thread ]
</a>
28 <a href=
"subject.html#3776">[ subject ]
</a>
29 <a href=
"author.html#3776">[ author ]
</a>
34 <PRE>On Tuesday, Apr
15,
2003, at
18:
16 US/Pacific, Ian R. Justman wrote:
36 ><i> Finny Merrill wrote:
37 </I>>><i> On Thu,
10 Apr
2003 17:
43:
56 +
0200, Dylan v.d Merwe
38 </I>>><i> <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">dylanvdm at icon.co.za
</A>> wrote:
39 </I>>>><i> The days have long passed when services used to act like bots and
40 </I>>>><i> sit in
41 </I>>>><i> channels. It is now against the irc protocol to allow this,
42 </I>>>><i> therefore it
43 </I>>>><i> does not happen nor can you set them to do so in the config file.
45 </I>>>><i> You can force services into a channel using RAW commands but this is
46 </I>>>><i> highly
47 </I>>>><i> discouraged as all sorts of things can go wrong. Leave them where
48 </I>>>><i> they are,
49 </I>>>><i> you'll be just fine.
51 </I>>>><i> Dylan.
52 </I>>><i> Whoa, when did it become against the irc protocol to do this? And
54 </I>>><i> irc protocol anyway? :p
56 </I>><i> Best thing I can gather is RFC
2813 section
2.2.2 which reads as
59 irc2's concept of a
"service
" is rather different from the concept of
60 a service most people on this list are used to. In irc2, it's a special
61 connection, neither client nor server. Methods for addressing it are
64 That might be what Dylan was referring to, but it doesn't apply to
67 ><i> Though also, I've seen Hybserv's Services' nicks join channels on two
69 </I>><i> Hybrid/Hybserv networks. I don't entirely see the point of that
72 Classic hybrid requires a client to be in the channel to actually
74 actions such as topic changes. It's born from way too many backwards-
75 compatibility requirements...
85 <LI>Previous message:
<A HREF=
"003774.html">[IRCServices] Services in channel opers
87 <LI>Next message:
<A HREF=
"003742.html">[IRCServices] Services
5.0.16 and
4.5.45 released
89 <LI> <B>Messages sorted by:
</B>
90 <a href=
"date.html#3776">[ date ]
</a>
91 <a href=
"thread.html#3776">[ thread ]
</a>
92 <a href=
"subject.html#3776">[ subject ]
</a>
93 <a href=
"author.html#3776">[ author ]
</a>