Re: Re: Alleged hijacking
  By: Earl Croasmun to Joe Delahaye on Thu Jun 16 2016 13:34:20

 EC> It seems like there is a very easy to avoid that ever happening. If the
 EC> echo tag was already listed in a nice, convenient, easily accessible list
 EC> of echoes, the duplication would never happen.

Of course, but, and it is a big BUT. List keepers over time have been known to
favour one side over the other.  As well, at least one such, was watching when
an echo listing expired, and just past the grace period by even a second, had
elisted it himself, sometimes without expiry warnings.  It is no wonder that
many (even in this zone) do not trust the Elist.


 EC> As for your statement "I think it is wrong," I understand
that opinion and
 EC> I respect it. But I can think of at least two very different reasons WHY
 EC> it could  be considered wrong.

 EC> Pragmatically, it could cause bleed-over between the two echoes: people
 EC> posting 
 EC> in one thinking it was the other, some systems dropping posts from both
 EC> into the same message base, general confusion. But in this instance it was
 EC> a private 
 EC> echo, only in one zone, and "made available by moderator
invitation-only."

 EC> Or you might think it is wrong because it is not polite to the moderator
 EC> in the 
 EC> "different zone." I suppose that if politeness were a
criterion to be on
 EC> the list, there would have never been echoes with names like
"Wittless"
 EC> (not subtle 
 EC> at all) or "Spot on Our Lungs" (subtle only to those who
do not know the
 EC> backstory).

It was wrong for one reason only.  Roy wanted piss of Michiel, and others in
Z2.  He accomplished his goal by being allowed to own that tag.  The Elist is
supposed to prevent stuff like that, but in this case made it possible, because
some do not wish to elist their echos.  It was not an international echo, so
really no need to do so.


 EC> But if people in that zone ignore the echolist, how would they even know
 EC> of the impoliteness? 

By reading the announcements in the Elist, and Backbone echos perhaps?
--- SBBSecho 3.00-Win32