Subj : Re: zone 4 ping
To : Fernando Toledo
From : Dan Clough
Date : Fri Apr 12 2024 03:20 pm
-=> Fernando Toledo wrote to Dan Clough <=-
FT> El 22/2/24 a las 00:08, Dan Clough escribió:
> -=> Ward Dossche wrote to Dan Clough <=-
> DC> It's hard to imagine a scenario where there could be a better time.
> WD> Let me try it another way, suppose as IC I would decide to
> WD> replace ZC1 just like that.
> That would be a whole 'nother situation, and that replacement would not
> be justified. The difference here, of course, is that the ZC in
> question has disappeared and is un-reachable. Seems like reasonable
> time and effort has been dispensed in *TRYING* to reach him. At what
> point does that unacceptable behavior (and Zone status) become something
> that needs decisive action to correct? Is it allowed to go on
> indefinitely? Seems stupid to allow that, as it clearly is not good for
> the health of FidoNet.
FT> Exactly, this is not a power dispute... we are just a few crazy
FT> nodes. It's a technical issue, I want the things to work.
FT> And when they don't work, they can be made to work and not expect
FT> that one person, because they are busy with other matters, will
FT> leave the entire area adrift.
I agree. And if that person can't be reached, he gets replaced whether
he likes it or not.
> WD> How successful do you think I would be?
> Not very, for reasons discussed just above. There's no defend-able
> reason to replace that ZC, but there is for the other.
> WD> The IC is a toothless tiger ... that has been demonstrated in the
> WD> past.
> There's an old saying that I've heard (and used a few times): Sometimes
> it's better to ask forgiveness than to seek permission. I don't see how
> anyone in FidoNet would think this (replacing the AWOL ZC) is not a
> justified and necessary action. It's for the betterment of FidoNet.
FT> It is not necessary for the IC to change to the ZC, but rather
FT> the ZC must come clean and step aside, leaving others to continue
FT> holding the zone while he cannot do so.
Well, as I understand it, he cannot be reached, or will not respond. If
that's the case he should be thrown out. If he will respond to you, I'd
suggest you ask him to do just that (step aside) so that he can be
replaced. It's been *WAY* longer than any reasonable person would think
is enough time to fix his broken Zone.
... So easy, a child could do it. Child sold separately.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
