]> jfr.im git - irc.git/blame - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001655.html
init
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 001655.html
CommitLineData
3bd189cb
JR
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2<HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] operserv / akill
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20operserv%20/%20akill&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="001702.html">
11 <LINK REL="Next" HREF="001693.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] operserv / akill</H1>
15 <B>Noam M.</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20operserv%20/%20akill&In-Reply-To="
17 TITLE="[IRCServices Coding] operserv / akill">noam_m at bezeqint.net
18 </A><BR>
19 <I>Fri Oct 25 17:39:12 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001702.html">[IRCServices Coding] Chanserv Chan Comand Problems
22</A></li>
23 <LI>Next message: <A HREF="001693.html">[IRCServices Coding] operserv / akill
24</A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1655">[ date ]</a>
27 <a href="thread.html#1655">[ thread ]</a>
28 <a href="subject.html#1655">[ subject ]</a>
29 <a href="author.html#1655">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33<!--beginarticle-->
34<PRE>----- Original Message -----
35From: &quot;CyberDems&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">cyberdems at wwirc.za.org</A>&gt;
36To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>&gt;
37Sent: Saturday, October 26, 2002 1:01 AM
38Subject: Re: [IRCServices Coding] operserv / akill
39
40
41&gt;<i> I will have to interfere here.
42</I>&gt;<i> UltimateIRCD is crap. no offence. It is CRAP. I'll give you an example
43</I>why.
44&gt;<i> try doing a /lusers request. You will get BOLD in certain areas, and
45</I>&gt;<i> underlined text, etc. Many IRC Clients (old ones especially) do not
46</I>support
47&gt;<i> colour, bold, underlined, inversed, etc text formats.
48</I>&gt;<i> UnrealIRCD and UltimateIRCD both have too many usermodes. such as *, %,
49</I>etc.
50&gt;<i> in clients such as mIRC, if you do a /whois on a user with one of those
51</I>&gt;<i> usermodes, you can't simply go over the channel name with your cursor and
52</I>&gt;<i> double-click it, because mIRC was not designed for such &quot;addons&quot;.
53</I>&gt;<i> UnrealIRCD has changed so many things, that half the services in the world
54</I>&gt;<i> do not work correctly with the newer versions, such as the Selene
55</I>versions.
56&gt;<i> Have you ever tried installing BOPM (blitzed open proxy monitor) on an
57</I>&gt;<i> Unreal IRCD server - it's mission impossible, all those patches?
58</I>&gt;<i> Yes, the coders have worked extra hard to get these extra un-necessary
59</I>&gt;<i> addons into the ircds, but think of it this way, how many IRCDs are there,
60</I>&gt;<i> and how many CLIENTS are there? The client coders have to do research on
61</I>the
62&gt;<i> IRCDs and then edit the clients to suite them. This is un-necessary, in my
63</I>&gt;<i> opinion. But like you said, Dylan, each to his own. So those of you
64</I>enjoying
65&gt;<i> your 200 users on that little UnrealIRCD slow network(s), keep going - I
66</I>&gt;<i> wish you many netsplits in the near future ;)
67</I>&gt;<i>
68</I>&gt;<i> --CyberDems
69</I>&gt;<i> irc.wwirc.za.org
70</I>&gt;<i>
71</I>
72i did not see one thing in your email that refers to UltimateIRCd3
73Ultimate2.8 is an old project and ShadowMaster urges all people to move to
74the next version, the version based on bahamut.
75about control codes in /lusers - that doesnt exist in ultimate3.
76usermodes *% never exists. they _were_ used as symbols to mark channel modes
77on users, and the symbol % that marks halfop is supported by more and more
78clients these days.
79Ultimate3 alpha 26 (the latest) uses the sign '!' to mark channel admins -
80the only sign supported by mIRC AND XChat.
81
82
83
84</PRE>
85
86<!--endarticle-->
87 <HR>
88 <P><UL>
89 <!--threads-->
90 <LI>Previous message: <A HREF="001702.html">[IRCServices Coding] Chanserv Chan Comand Problems
91</A></li>
92 <LI>Next message: <A HREF="001693.html">[IRCServices Coding] operserv / akill
93</A></li>
94 <LI> <B>Messages sorted by:</B>
95 <a href="date.html#1655">[ date ]</a>
96 <a href="thread.html#1655">[ thread ]</a>
97 <a href="subject.html#1655">[ subject ]</a>
98 <a href="author.html#1655">[ author ]</a>
99 </LI>
100 </UL>
101
102</body></html>