Subj : File, file; who's got the file To : David Calafrancesco From : Jack Yates Date : Thu Aug 30 2001 12:30 am JY>> group complain about her polluting the FDN. Foxy apologizes and JY>> ceases the practice, and sets up a separate FDN for this JY>> particular purpose; the Distribution systems and downlinks now DC> She didn't create a new FDN, she merely used her status as ZEC to DC> hatch in the REC's regional routing list FDN. However it happened (and there have been several versions which just goes to show that my memory is as faulty as anyone's) the file was moved from BACKBONE upon request. DC> I suppose if she wanted DC> to she could appoint the IRN Route committee the status of 'official DC> loyal opposition' route list and it too could be legit for Z1_REC. Or DC> one of the 10 RECs might decide that it is an accurate representation DC> of their region and endorse it and hatch it there as well. But that DC> hasn't happened. Would it solve this problem without creating another? If it would, I wouldn't be adverse to the idea. DC> Those who complained, complained about the release... the location was DC> irrelevant. The fact of releasing something that he had no right to DC> release was the overriding factor. JY>> Then Ross releases backbone files pertaining to his system in JY>> BACKBONE, people complaing that he's polluting the FDN. Ross JY>> apologizes, stops the practice and all is well. DC> I must have missed that... where was the witch hunt? I haven't seen it DC> here... I guess there wasn't one, or somebody tried to give a witch-hunt and nobody came. My error. DC> As the 'official' route list has a history of gross innaccuracies with DC> regards to connections to and from most Z1B hubs, yes, we determined DC> that this other routing file was an important info file for our DC> operations. Ummm...ERNROUTE wasn't very accurate upon its inception either, IIRC. It's my belief that both files got better with time. DC> Then I reserve the right to create additional echos to move echomail DC> from certain people I and my down links don't want to see. It isn't DC> right when applied to echomail, nor is it right when applied to files. What you suggest here is a twit filter of sourts. David, I understand what you're trying to convey here, but I don't quite agree with your analogy. Messages between/among people in this echo are inter-related, IRNROUTE and the backbone/backstat files are not. Traditionally, the remedy for objectionable messages in an echo is to de-link the complainant from the echo altogether. I can't do this with BACKBONE, my donlinks depend on the other files in the FDN, and I have one link who wants to receive IRNROUTE and I read it over myself so cutting the FDN from the complaining downlink or deleting the file is not an option. Were the file intertwined with the other files in BACKBONE, I would agree with you. --- McGuffey's Reader GoldED UNREG * Origin: (1:3613/1275.1) .