Subj : Third Party Updates
To   : Thom LaCosta
From : Roy Witt
Date : Tue Sep 05 2000 11:05 am

Hello Thom.

05 Sep 00 17:28, you wrote to me:

 TL>> As I've told you in netmail, and in various public announcements,
 TL>> unless a moderator confirms with me that he/she wants you to do the
 TL>> updates, they will NOT be processed.

 RW>> If there's been no response from the moderators of these echos,
 RW>> that'll be the best thing to happen to them anyway. Once those
 RW>> echos expire, Bobby can 'rescue' them and name himself as moderator
 RW>> and we can start this process all over again.

 TL> The correct term is relist...there is no such thing as rescue.

I stand corrected. Even if that's the term I've been reading.

 RW>> Or is there now
 RW>> going to be a new rule that you can't rescue an echo and name
 RW>> yourself as the moderator, even though the previous moderator can't
 RW>> be found?

 TL> No, but you can't relist an echo and hide behind someone else's name.

You mean the previous moderator's name.

 TL> All one needs to do is relist the echo with him/her self as
 TL> moderator...give up the rescue pretense and acccept whatever
 TL> criticism, if any, for amassing a large collection of echo tags.

Sounds like a plan.

 TL> Once that's done, it's pretty clear when a dead echo is re-boned, or
 TL> re-named, or killed off that the person doing is is the moderator,
 TL> not some third party.

As a third party, I do all of this.  I do it for someone who's not
interested in learning the Z1 elist procedures, nor having to deal
with either NA backbones.  All he cares about is whether his echo is boned
and available in Z1, as well as protected from echo tag pirates.  He had
no objection to me putting myself in the moderator list and he get's his
copy of the update (password included) everytime I do it.  Seems to me
this is going to be the only way around the 'no third party' rule.

 RW>> This is getting sillier by the day...

 TL> Sure is...and the silliness stems from folks distorting the
 TL> expiration dates and accuracy of the echolist.

How so?  Echolist tag expiration is set by the robot when it receives a
MOD UPD with the correct password.  All other attempts are ignored, accept
for the 'pirate' warning it sends to the elisted moderator.  I proved that
to myself this past weekend, doing some echo deletions.   Reading the
echolist updates posted in ECHOLIST, all one has to do is observe the line
which tells us 'who' updated the tag.


.... Lookout World!  The Modem is Ringing!
--- Twit(t) Filter v2.1 (C) 2000
 * Origin: **  Moderator - CBRADIO  ** (1:10/22)

.