Subj : Re: Remember To : Matt Bedynek From : Janis Kracht Date : Fri Aug 24 2001 04:27 pm Hi Matt, >>> So who is/are the person(s) directly responsible for it now? >> If anyone could be called responsible for it, it would be the NAB in >> my opinion, since it was initially a NAB vehicle. > As David pointed out, Souvestre was the only remaining one of the original > creators. The case could be made that it belonged to him since the others > left. "He" didn't create it. "He" was part of a group that created it. When he left that group, he started his own "group", his choice, but that does not diminish the fact of the original group's creation of the area. I don't understand why some people are continuing to push this particular topic which is sure to only create more anger amongst the two distributions. In any case, and in fact I originally spoke of no one distribution "owning" the file echo: when you asked, as I said earlier, in my opinion the NAB would be responsible for the area, since it was created by them, but I never stated "it is a NAB file echo" insinuating that the NAB should or would control it. Any file distributed in that file echo is done out of cooperation between the distribution systems involved. Or at least, that is the way it SHOULD be. Cooperation between the distributions means more than just "I'll feed you, you feed me". It also means "I won't pass any files in this area which do not belong, and you will not pass any files in this area which do not belong". David and Dale are stretching the description of this file echo to allow the release of their routing file and it is not necessary. The idea of shared file echos goes way back.. long ago the PDN and Fernwood shared a file echo to prevent duplicate files from being released for instance. The BACKBONE file echo is a shared file echo amongst distribution systems and so is a little different but still cooperation is expected among those who use it. > I prefer that the fileecho be touted as an open medium to any BACKBONE > and not controlled by any group. That is the reason I've been pushing for a separate FDN for the IRNRoute list. It is the only way to remove political shenanigans in the area by any one distribution. If the WWB started releasing it's routing file in the BACKBONE file echo, I would be asking them to also create a separate FDN or file echo to handle it. If Gamesnet started releasing it's routing file (and they've got quite an extensive membership and nodelist) I would point them to their own FDN to create an appropriate file echo to handle it. >> Since the NAB created the file echo, I would say that the one >> party responsible for it would be the NAB. >Let this be the beginning of a new war over who offically controls the BACKBON > fileecho. I wonder which way this one will go....hmmm... I don't think that is going to happen. Either David and Dale will create a file echo for their IRNRoute list or they won't. I still haven't gotten any reason from them to explain what would be so bad about having their own file echo. >> Prevent them? I don't see a way to do that nor would I care to. I've >> been working to stop them to no avail but through discussion. > But why? Because the file they are releasing in that area does not belong there. No routing file belongs in that file echo. >> Would you like me to add up the number of netmail and echomail >> correspondance to Dale and David regarding creating their own fdn? > I'm quite aware of how politics in Z1 work. :-( You mentioned earlier that you also believed the IRNRoute list belonged in it's own area. I still think it does. I think you do as well. >> If you are refering Ross here, he is moving the file to an area so >> that his downlinks are not continually annoyed at the file's presence. > I'm surprised you would endorse this action. I see it as one means of making something work on his system, since the Z1B refuses to define their own file echo for the file they are releasing. When Foxy was asked to stop releasing the routing file that she maintains in the BACKBONE file echo, she did. Whoever is creating the IRNRoute list should do the same. > It seems that Ross has only > considered the impact of his action locally. I'm sure there are those that > feed well below his system. >> He let me know he was doing it. It doesn't bother me as long as >> the file gets out, and his downlinks are aware of what he is doing >> (they are). > What about the downlinks below his downlinks? And further? You don't believe his downlinks are telling their downlinks about the file echo he's moved the file to? I bet they are. Again, I don't see this as a problem. If the file was being deleted, or tampered with in terms of content you can bet I'd have something to say. >> If David, Dale or someone in authority in the Z1B doesn't create a >> new fdn for this list by this weekend, I may do the same. > *sigh* If you think this is tiresome, you should be here trying to get a simple file echo created. Sorry, on my system the area will be well documented and clearly defined as it should be. >> See, that is you, and that's ok - but your downlinks some day may not >> feel the same way as you do. They may get irritated at this file >> continually appearing in the BACKBONE file echo and you may decide to >> also move the file to another area. >A case could be made for *any* file hatched into an area and that is where you >begin to trek on thin ice. Its a very dangerous thing and could escilate into > a problem nobody in Z1 (or fidonet) is willing or capable of dealing with. No, I don't think so. One of the problems with the backbone file echo is it's entry point into distribution. It comes from various sources via HUBs into the distribution. Other file echos come in here, for example, and then go out. >> An archive would be a pain for those using it I would think. The WWB >> releases separate files (BACKBONE.WW, etc...). Not sure I follow you >> here :) > It used to release them in a serialized archive. Perhaps this has changed? It comes in via Barry as a zip file with no .tic file. The zip file contains the .WW files and their .TIC files. Take care, Janis --- BBBS/LiI v4.01 Flag-3 * Origin: Prism bbs (1:2320/38) .