Subj : Echo Savior Rides Again
To   : ANDREA SANTOS
From : Roy Witt
Date : Sat May 12 2001 10:57 am

Hello ANDREA.

12 May 01 11:25, you wrote to me:

 AS> -> By not allowing a third party update for 30 days after expiration,
 AS> the -> echo users can then be notified in the echo.  There's no need
 AS> to disrupt -> an echo just because the moderator has flown the coupŠ.

 AS> Okay, so you're saying to simply day the echo notification?  If so, I
 AS> can go along with that.

Delay it until the expiration, yes.  Then the echo users can decide what
to do while the echo is protected from 'saviors' for thirty days.  Perhaps
the savior can talk the users into allowing him to elist it or assist
them in doing so if they decide otherwise.

 AS> -> Even under SLA rules, the echo will be in distribution for six
 AS> months -> after it's been dropped from the elist.  There's no hurry.

 AS> But the password can be gotten prior to that.

Under the present circumstances, there's no elisting once it's expired
and anyone can update it.  If there was a thirty day wait before anyone
could update the listing, no savior would be allowed to do so until the
31st day after expiration.

 AS> -> You're forgetting that the EK serves notice to moderators that
 AS> their -> elisting is about to expire, via netmail or email, whichever
 AS> is the case -> of the last update. The first being sent 30 days
 AS> before the echolisting -> will expire.

 AS> If this is the case, and I'm not sure I have all the messages onhand
 AS> in two places to check, I was not notified by any method when mine
 AS> almost expired.

You should have been. If you updated via netmail, then you got an ack via
netmail, routed I believe.

 AS>   Had sent in updates somewhere in the Fall of 2000.
 AS> Sent them again after 2001.  IIRC, Thom then routed mail for me to
 AS> Jerry Gause telling me I would need to resend the updates.
 AS> Unfortunately, Jerry's been MIA and I don't know why anyone was
 AS> routing to me through Jerry as John was my uplink.  At any rate, I
 AS> didn't get the message until someone woke Jerry up and he fixed his
 AS> system.  This was weeks before my echos were set to expire.

Yep. Many a moderator has lost an elisting due to routed netmail going
astray.

 AS> Prior to a year ago, I didn't carry ECHOLIST.  A former Net135
 AS> node, now user, asked me to, but I didn't have it turned on so had no
 AS> idea my echos didn't take.  I've never received email or netmail
 AS> notification from the EK confirming my echos were updated, so unless
 AS> you're reading ECHOLIST, you don't know.

Yes, you do.  I due updates by email.  I get an ack via email and have a
folder full of MOD UPD, MOD UPD ACK and RESEND requests from the EK.

 AS> -> However, echo users may construe certain knowledge that the echo
 AS> -> moderator doesn't have the elist password by his inaction to make
 AS> the -> update.

 AS> I wouldn't make that assumption.  Would only think he forgot or there
 AS> had been a glitch.

I made the assumption and was correct in doing so.

 AS> -> Some users, the really smart ones, would figure out after weeks go
 AS> by -> that the moderator didn't have the password to update the
 AS> listing. -> Hence, an echo hijacking takes place.

 AS> Rephase, users who want to hijack an echo. ;-)  Don't have to be
 AS> smart. <g>

OK, sly.

 AS> ->  AS> But then there is the complaint about "saviors".  Can't blame
 AS> the ->  AS> savior if nothing is being done so that it won't happen.

 AS> -> You got that right.

 AS> Hence no need for "echo savior" messages to be posted in 5 different
 AS> echos. ;-)

Isn't that silly?


.... Shelby or Alec. or any of the counltess nobodys in this echo. -jw-
--- Twit(t) Filter v2.1 (C) 2000
 * Origin: 1998 FLAME echo - Asshole Of the Year! (1:10/22)

.