TIP: Click on subject to list as thread! ANSI
echo: net_dev
to: Jan Vermeulen
from: Jesper Srensen
date: 2003-01-08 18:15:36
subject: Bad nodelist data

mb>> As I told you, you wont loose the data.

 JV>     Nor will it get to the top for integration in that week's and who
 JV> knows how mainy next weeks' nodelists. And that is a loss, not for me,
 JV> but for the net, because it spells loss of connectivity for that or
 JV> those unlisted or wrongly listed node AND all other correct changes
 JV> that were in that same list. Until I find out when coming home from a
 JV> holyday or the hospital.

I don't know how you do it but most *C:s I know would not submit a [broken]
segment, without first checking it for validity, without checking the
submission results and then make themselves unavailable for a couple of
weeks.

If a *C submits a broken segment, that's his fault and nobody else's. If I
should submit a broken segment (which I try not to) I would expect to have
it rejected so I could fix the problem and resubmit. Allowing programs to
automatically "fix" problems is very dangerous ground. "None
will thank you if it suceeds but many will flame you when it fails..."
;-)

Maintaining nodelist data is the primary job of *C:s and it's really not
that difficult (I'm a Fidonet NC and othernet RC so I know). If a *C can't
handle his job he should let someone else do it.

  Jesper,
  yeppe{at}enjoy.cc
---
* Origin: Singularity/2 - Swedish Internet Backbone (2:204/255)
SEEN-BY: 633/267 270
@PATH: 204/255 20/11 2411/413 2432/200 774/605 123/500 106/1 379/1 633/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™.