]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> AW: [IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%5D%20Is%20there%20a%20timeline%20in%20the%20future%20for%20supporting%20ircd2.9%20or%20greater&In-Reply-To=20020805.16594859%40jgdpd012.gyn.jorlan.com.br"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="003030.html"> | |
11 | <LINK REL="Next" HREF="003032.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>AW: [IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater</H1> | |
15 | <B>Yusuf Iskenderoglu</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%5D%20Is%20there%20a%20timeline%20in%20the%20future%20for%20supporting%20ircd2.9%20or%20greater&In-Reply-To=20020805.16594859%40jgdpd012.gyn.jorlan.com.br" | |
17 | TITLE="AW: [IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater">uhc0 at rz.uni-karlsruhe.de | |
18 | </A><BR> | |
19 | <I>Mon Aug 5 19:45:01 PDT 2002</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="003030.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="003032.html">AW: [IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#3031">[ date ]</a> | |
27 | <a href="thread.html#3031">[ thread ]</a> | |
28 | <a href="subject.html#3031">[ subject ]</a> | |
29 | <a href="author.html#3031">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Hi, | |
35 | ||
36 | though I am not an authority, I would say NO, because ircd2.10 | |
37 | and later is not designed to work with a services server | |
38 | (and not SERVICE's which are a totally different kind), | |
39 | because of the following: | |
40 | ||
41 | - Lack of a global kline (akill would not work) | |
42 | - Lack of topic burst | |
43 | - Lack of services-savvy functions like (SVSMODE, SVSNICK) | |
44 | - Lack of privilege level (like U:Line) so that certain clients | |
45 | can do more (kill, mode, kick, topic) without having to join | |
46 | channels. | |
47 | ||
48 | Unless IRCnet coders start coding their ircd to support services, | |
49 | I do not see any point in supporting that ircd, since the kludges | |
50 | and hacks to accomplish those mentioned functionality would take | |
51 | too much time. | |
52 | ||
53 | Example: | |
54 | - Instead of Autokilling, services would need to continously send | |
55 | KILL, and this would work as long as you configure your server | |
56 | to allow remote KILLs. | |
57 | - After a netjoin, a channel could have different topics the amount | |
58 | of linking servers, and services would never notice it, and | |
59 | it also would not need resetting topics. | |
60 | - Services would even not see a netsplit happening, if: | |
61 | bla.xxx.com splits from | |
62 | hub.xxx.com but, hub.xxx.com represents themselves as | |
63 | *.xxx.com and any server behind them is hidden from the | |
64 | network. | |
65 | - Guest'ing would not work, since SVSNICK is not there. | |
66 | - In order for ChanServ to MODE #channel +o nick, ChanServ should | |
67 | join the channel, and become op by services server, and then | |
68 | set op on another user | |
69 | - The same for kick and topic. | |
70 | ||
71 | Moreover, ircservices cannot be redesigned to work as SERVICE's, | |
72 | because a SERVICE is not differentiated by name, but <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">name at host</A>, | |
73 | and this would mean, that anyone could link up their NickServ | |
74 | to the net as a service, and the best_service() thing from | |
75 | IRCnet ircd would just choose ONE optimal choise for you, leading | |
76 | to total inconsistency with registration/access lists, etc. | |
77 | ||
78 | I am additionally not sure, whether IRCnets SERVICE's are allowed | |
79 | to MODE/KICK/TOPIC. | |
80 | ||
81 | Regards; | |
82 | yusuf | |
83 | ||
84 | PS: What is actually the main reason for you to use ircd2.10 or | |
85 | later ? I ask just because of interest. (You can answer me | |
86 | privately to this question, if you want) | |
87 | ||
88 | ------------------------------------------------------------------ | |
89 | |<i> Yusuf Iskenderoglu | You get to meet all sorts, | | |
90 | </I>|<i> eMail - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at stud.uni-karlsruhe.de</A>| in this line of work... | | |
91 | </I>|<i> eMail - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">s_iskend at ira.uka.de</A> | | | |
92 | </I>|<i> ICQ UIN : 20587464 \ TimeMr14C | | | |
93 | </I>------------------------------------------------------------------ | |
94 | ||
95 | ||
96 | ||
97 | ><i> -----Ursprüngliche Nachricht----- | |
98 | </I>><i> Von: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-admin at ircservices.za.net</A> | |
99 | </I>><i> [mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-admin at ircservices.za.net</A>] Im Auftrag von | |
100 | </I>><i> Frederico C Wilhelms Fred | |
101 | </I>><i> Gesendet: Montag, 5. August 2002 19:00 | |
102 | </I>><i> An: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A> | |
103 | </I>><i> Betreff: [IRCServices] Is there a timeline in the future for | |
104 | </I>><i> supporting ircd2.9 or greater | |
105 | </I>><i> | |
106 | </I>><i> | |
107 | </I>><i> Hi, | |
108 | </I>><i> | |
109 | </I>><i> Is there any kind of timeline for supporting newer versions of the | |
110 | </I>><i> ircd2.(>9) ? | |
111 | </I>><i> | |
112 | </I>><i> Tks | |
113 | </I>><i> | |
114 | </I>><i> Fred | |
115 | </I>><i> | |
116 | </I>><i> | |
117 | </I>><i> | |
118 | </I>><i> ------------------------------------------------------------------ | |
119 | </I>><i> To unsubscribe or change your subscription options, visit: | |
120 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo">http://www.ircservices.za.net/mailman/listinfo</A>> /ircservices | |
121 | </I>><i> | |
122 | </I> | |
123 | ||
124 | </PRE> | |
125 | ||
126 | <!--endarticle--> | |
127 | <HR> | |
128 | <P><UL> | |
129 | <!--threads--> | |
130 | <LI>Previous message: <A HREF="003030.html">[IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater | |
131 | </A></li> | |
132 | <LI>Next message: <A HREF="003032.html">AW: [IRCServices] Is there a timeline in the future for supporting ircd2.9 or greater | |
133 | </A></li> | |
134 | <LI> <B>Messages sorted by:</B> | |
135 | <a href="date.html#3031">[ date ]</a> | |
136 | <a href="thread.html#3031">[ thread ]</a> | |
137 | <a href="subject.html#3031">[ subject ]</a> | |
138 | <a href="author.html#3031">[ author ]</a> | |
139 | </LI> | |
140 | </UL> | |
141 | ||
142 | </body></html> |