TIP: Click on subject to list as thread! ANSI
echo: moderator
to: Jeff Smith
from: Thom LaCosta
date: 2008-03-10 10:17:52
subject: Echos?

Jeff Smith wrote in a message to Thom LaCosta:


 JS>>     Now you've done it.  I would be concerned about placing
 JS>> limits decided on by one or a few people. If the majority of the
 JS>> users agreed to a limit then I would be ok with it. Maybe a
 JS>> longer time period between when echos expire and when they can be
 JS>> updated/added by someone OTHER than the listed updater/moderator.

 TL> That was tried in the past(a grace period)....it simply menat that the
 TL> folks who wanted to relist an echo just waited a bit longer to do it.

 JS>      That's the problem. If a grace period was used as intended for
 JS> those that occasionally for whatever reason don't get their update
 JS> in then ok. 


There is no need for a grace period.  Moderators have six months to make an
update...it is such a simple task that having a grace period is beyond
common sense.  The moderators who care about their listings maintain their
listings, and the bulk of those that do that don't wait until the sixth
month to update...they do it on a more frequent basis.

There are numerous applications that can automate the task, and there are
even folks who will submit updates for a moderator.  There have even been
folks in the past who actually falsified the node number of the moderator
to make it appear that the moderator had submitted the update.  One giy was
real close to loosing his nodenumber over that little game.

 JS> specific X number of days. During that inactive period the only
 JS> person that could update that echo would be the listed moderator
 JS> and/or their messenger. Beyond that time the echo tag would be
 JS> available to anyone to update.

But all that is simply not required is the moderator fullfills his/her
responsibility to update the echo.

 JS>> BTW, Thom I never received the message from you that Jeff is
 JS>> replying to.

 TL> Hmmmmmm,  I send everything to Ross....so if some folks see the
 TL> messages and some don't, there may be a broken link beyond Ross's
 TL> system.

 JS>      I get mail from Bob Seaborn. I also didn't see your "Sync
 JS> Echo" message in the Sync echo if you (re)posted it. Course that
 JS> echo is now passthrough here.

Well, it looks like there is a problem somewhere between you and Ross...and
if it's Bob Seaborn, you might ask him to look into it.

 TL> cya,
 TL> thom
 TL> http://www.echolist.net/
 TL> --- GEcho 1.20/Pro

 JS> Jeff

 JS> ___ GoldED+/W32-MINGW 1.1.5-b20070503
 JS>  - Origin: Twin_Cities_Metronet - region14.us (1:14/5)

cya,
thom
http://www.echolist.net/ 
--- GEcho 1.20/Pro
TL> * Origin: Home of The Other Robot (1:261/1352)
* Origin: Home of The Other Robot (1:261/1352)
SEEN-BY: 10/1 3 14/300 34/999 53/558 90/1 116/901 120/228 123/500 134/10 140/1
SEEN-BY: 222/2 226/0 236/150 249/303 261/20 38 100 1381 1404 1406 1418
SEEN-BY: 280/1027 320/119 396/45 633/104 260 262 267 285 712/848 800/432
SEEN-BY: 801/161 189 2222/700 2320/100 2905/0
@PATH: 261/1352 123/500 261/38 633/260 267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.