1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> Re Strider: [IRCServices] More suggestions
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=Re%20Strider%3A%20%5BIRCServices%5D%20More%20suggestions&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=
"001664.html">
11 <LINK REL=
"Next" HREF=
"001662.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>Re Strider: [IRCServices] More suggestions
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=Re%20Strider%3A%20%5BIRCServices%5D%20More%20suggestions&In-Reply-To="
17 TITLE=
"Re Strider: [IRCServices] More suggestions">strider at chatcircuit.com
19 <I>Wed Mar
21 13:
10:
04 PST
2001</I>
21 <LI>Previous message:
<A HREF=
"001664.html">Re Strider: [IRCServices] More suggestions
23 <LI>Next message:
<A HREF=
"001662.html">[IRCServices] More suggestions
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1665">[ date ]
</a>
27 <a href=
"thread.html#1665">[ thread ]
</a>
28 <a href=
"subject.html#1665">[ subject ]
</a>
29 <a href=
"author.html#1665">[ author ]
</a>
34 <PRE>Some good points, but not why I would disagree. Some of the people who make
35 modifications are not as well versed in C as others, I am one who isn't.
36 Some of the modifications we made were cosmetic, but we did add a extremely
37 stripped down bots service to
4.4.8. Once I have time to spare, I may work
38 on it a bit more, but I am sure it will require a lot of work to move it
39 over to
4.5.x. I may just wait for
5.0 when the modular support is added and
40 make the bots code a module (it practically is, with minor hacks to
2
41 different files, one being the makefile, and the rest being in its own
42 contained .c). The code is far from clean or efficient. I am rather
43 surprised the bots addition hasn't brought down our network for a while (it
44 use to repeatedly until I fixed a
"stupidity bug
").
46 Beau (Strider) Steward
47 chatcircuit administrator and
6bit band member
48 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">strider at chatcircuit.com
</A> www.chatcircuit.com
49 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircadmin at chatcircuit.com
</A> irc.chatcircuit.com
50 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">strider at
6bit.net
</A> www
.6bit.net
51 ----- Original Message -----
52 From:
"Yusuf Iskenderoglu
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at rz.uni-karlsruhe.de
</A>>
53 To:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
54 Sent: Wednesday, March
21,
2001 4:
15 AM
55 Subject: Re: Re Strider: [IRCServices] More suggestions
61 </I>><i> On Wed,
21 Mar
2001, Partizanu wrote:
64 </I>><i> > Interesting thing, I see lots of people doing modifications on
66 ><i> > you (all coders) would like to share `em? :)...Like makeing a page with
68 ><i> > modification on services (not only by you)...maybe Mr Andrew Church
70 ><i> > `em and include `em in a future release? What do you say? Bad idea?
73 </I>><i> I do not see this necessary. If someone claims that a specific feature is
74 </I>><i> really useful, then they post it to the list, people discuss about it, and
75 </I>><i> Mr. Church finds a good way to implement it, if aggreed on inclusion.
77 </I>><i> There are too many networks, which use a modified version of services, or
78 </I>><i> even a modified ircd for some purposes. Or even changes are specific to
79 </I>><i> the ircd they use. Changes that are globally applicable to services
80 </I>><i> already manage to get included with it.
82 </I>><i> You also have to keep in mind, that if such an information is included on
83 </I>><i> the main webpage, people will not stop themselves from asking the main
84 </I>><i> coder for a support of a specific patch that patched another patch, that
85 </I>><i> patched a bug, which will definitely become annoying. You also must see,
86 </I>><i> that the coder of the given patch may not be available. That way, the one
87 </I>><i> who is designing the webpage, has to make bookkeeping, whether a patch is
88 </I>><i> actual, whether there are newer versions,, whether a link is functioning,
89 </I>><i> whether a patch is applicable to the current release, whether it is
90 </I>><i> already included.....
96 </I>><i> Yusuf Iskenderoglu *** eMail
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at rz.uni-karlsruhe.de
</A>
99 </I>><i> -----------------------------------------------------------
100 </I>><i> To unsubscribe, mail
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net
</A>
101 </I>><i> with the word UNSUBSCRIBE in the subject of the mail.
102 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
113 <LI>Previous message:
<A HREF=
"001664.html">Re Strider: [IRCServices] More suggestions
115 <LI>Next message:
<A HREF=
"001662.html">[IRCServices] More suggestions
117 <LI> <B>Messages sorted by:
</B>
118 <a href=
"date.html#1665">[ date ]
</a>
119 <a href=
"thread.html#1665">[ thread ]
</a>
120 <a href=
"subject.html#1665">[ subject ]
</a>
121 <a href=
"author.html#1665">[ author ]
</a>