]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2004/004581.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2004 / 004581.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] +O overrideable by non-opers in UnrealIRCd netmerge
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20%2BO%20overrideable%20by%20non-opers%20in%20UnrealIRCd%20netmerge&In-Reply-To=411E9383.2010104%40starglade.org">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="004578.html">
11 <LINK REL="Next" HREF="004579.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] +O overrideable by non-opers in UnrealIRCd netmerge</H1>
15 <B>Medice</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20%2BO%20overrideable%20by%20non-opers%20in%20UnrealIRCd%20netmerge&In-Reply-To=411E9383.2010104%40starglade.org"
17 TITLE="[IRCServices] +O overrideable by non-opers in UnrealIRCd netmerge">medice at gmx.at
18 </A><BR>
19 <I>Sat Aug 14 16:03:36 PDT 2004</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="004578.html">[IRCServices] +O overrideable by non-opers in UnrealIRCd netmerge
22 </A></li>
23 <LI>Next message: <A HREF="004579.html">[IRCServices] +O overrideable by non-opers in UnrealIRCd
24 netmerge
25 </A></li>
26 <LI> <B>Messages sorted by:</B>
27 <a href="date.html#4581">[ date ]</a>
28 <a href="thread.html#4581">[ thread ]</a>
29 <a href="subject.html#4581">[ subject ]</a>
30 <a href="author.html#4581">[ author ]</a>
31 </LI>
32 </UL>
33 <HR>
34 <!--beginarticle-->
35 <PRE>&gt;<i> This is how the local oper has been working, since opers were first
36 </I>&gt;<i> added to the ircd. It's nothing new to Unreal.
37 </I>&gt;<i>
38 </I>well i don't have on a bright knowledge of ircds and their history in
39 detail, but I don't believe that this is good working that way...
40 I personally don't like the idea of localops at the first place
41 (different story), but if there is such a thing it should work smoothly
42 - and if there are new developments which depends on previous
43 installations , than it might be necessary to make some minor or major
44 adjustments - even to old well-known stuff
45 f.e. chanmode +O (which is rather new I think - considering history of
46 IRC ;) ) blocking every non-oper, which means there must be a clear
47 detection either a user is an oper or not - if there are cross-checks on
48 remote servers if they are - or not, than they have to be informed
49 correctly as well...
50
51 but at first this was not about the localop/chmode+O-problem but about
52 netsplits and net(re)connects - also a rather well known thing which
53 always caused problems on networks (desync/overtaking/etc...)
54 I think an ircd should work smoothly on its own - services just offer
55 additional features and are not responsible to clean up ircd's desyncs
56
57 As I mentioned on unreal-bug-tracker on this topic &quot;the fact that
58 something works as designed does not mean, that the design hasn't any
59 flaws...&quot;
60
61 greets
62 /medice
63
64
65 </PRE>
66
67 <!--endarticle-->
68 <HR>
69 <P><UL>
70 <!--threads-->
71 <LI>Previous message: <A HREF="004578.html">[IRCServices] +O overrideable by non-opers in UnrealIRCd netmerge
72 </A></li>
73 <LI>Next message: <A HREF="004579.html">[IRCServices] +O overrideable by non-opers in UnrealIRCd
74 netmerge
75 </A></li>
76 <LI> <B>Messages sorted by:</B>
77 <a href="date.html#4581">[ date ]</a>
78 <a href="thread.html#4581">[ thread ]</a>
79 <a href="subject.html#4581">[ subject ]</a>
80 <a href="author.html#4581">[ author ]</a>
81 </LI>
82 </UL>
83
84 </body></html>