]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Services in channel opers | |
5 | </TITLE> | |
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="> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="003747.html"> | |
11 | <LINK REL="Next" HREF="003776.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Services in channel opers</H1> | |
15 | <B>Ian R. Justman</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20in%20channel%20opers&In-Reply-To=" | |
17 | TITLE="[IRCServices] Services in channel opers">ianj at esper.net | |
18 | </A><BR> | |
19 | <I>Tue Apr 15 18:16:37 PDT 2003</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="003747.html">[IRCServices] Services in channel opers | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="003776.html">[IRCServices] Services in channel opers | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#3774">[ date ]</a> | |
27 | <a href="thread.html#3774">[ thread ]</a> | |
28 | <a href="subject.html#3774">[ subject ]</a> | |
29 | <a href="author.html#3774">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE> | |
35 | ||
36 | Finny Merrill wrote: | |
37 | ><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> | |
40 | </I>>><i> The days have long passed when services used to act like bots and sit in | |
41 | </I>>><i> channels. It is now against the irc protocol to allow this, therefore it | |
42 | </I>>><i> does not happen nor can you set them to do so in the config file. | |
43 | </I>>><i> | |
44 | </I>>><i> You can force services into a channel using RAW commands but this is | |
45 | </I>>><i> highly | |
46 | </I>>><i> discouraged as all sorts of things can go wrong. Leave them where they | |
47 | </I>>><i> are, | |
48 | </I>>><i> you'll be just fine. | |
49 | </I>>><i> | |
50 | </I>>><i> Dylan. | |
51 | </I>><i> Whoa, when did it become against the irc protocol to do this? And which | |
52 | </I>><i> irc protocol anyway? :p | |
53 | </I> | |
54 | Best thing I can gather is RFC 2813 section 2.2.2 which reads as follows: | |
55 | ||
56 | 2.2.2 Services | |
57 | ||
58 | Each service is distinguished from other services by a service name | |
59 | composed of a nickname and a server name. The nickname has a maximum | |
60 | length of nine (9) characters. See the protocol grammar rules | |
61 | (section 3.3.1) for what may and may not be used in a nickname. The | |
62 | server name used to compose the service name is the name of the | |
63 | server to which the service is connected. In addition to this | |
64 | service name all servers MUST know the service type. | |
65 | ||
66 | Services differ from users by the format of their identifier, but | |
67 | more importantly services and users don't have the same type of | |
68 | access to the server: services can request part or all of the global | |
69 | state information that a server maintains, but have a more restricted | |
70 | set of commands available to them (See "IRC Client Protocol" [IRC- | |
71 | CLIENT] for details on which) and are not allowed to join channels. | |
72 | Finally services are not usually subject to the "Flood control" | |
73 | mechanism described in section 5.8. | |
74 | ||
75 | But then again, Andy does not recognize the IRCnet RFCs (which is what I | |
76 | call them since these documents were written by an IRCnet staffer) as being | |
77 | official, so... | |
78 | ||
79 | Though also, I've seen Hybserv's Services' nicks join channels on two | |
80 | different Hybrid/Hybserv networks. I don't entirely see the point of that | |
81 | myself. | |
82 | ||
83 | --Ian R. Justman, Co-Founder and Postmaster, The EsperNet IRC Network. | |
84 | ||
85 | ----- | |
86 | Ian R. Justman <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ianj at esper.net</A> (Official EsperNet business) | |
87 | Co-Founder and Postmaster, The EsperNet IRC Network | |
88 | Server Administrator, chocobo.esper.net "IJ" on IRC | |
89 | ||
90 | PGP/GPG keys available upon request, or from any PGP keyserver. | |
91 | ||
92 | </PRE> | |
93 | ||
94 | <!--endarticle--> | |
95 | <HR> | |
96 | <P><UL> | |
97 | <!--threads--> | |
98 | <LI>Previous message: <A HREF="003747.html">[IRCServices] Services in channel opers | |
99 | </A></li> | |
100 | <LI>Next message: <A HREF="003776.html">[IRCServices] Services in channel opers | |
101 | </A></li> | |
102 | <LI> <B>Messages sorted by:</B> | |
103 | <a href="date.html#3774">[ date ]</a> | |
104 | <a href="thread.html#3774">[ thread ]</a> | |
105 | <a href="subject.html#3774">[ subject ]</a> | |
106 | <a href="author.html#3774">[ author ]</a> | |
107 | </LI> | |
108 | </UL> | |
109 | ||
110 | </body></html> |