Subj : Remember To : Dale Ross From : Ross Cassell Date : Fri Aug 24 2001 12:51 pm Hello Dale! 24 Aug 01 18:52, you wrote to Michael Grant: DR> Area BACKBONE 0 !* FidoNet: Echomail Area Lists and Info Which has implied from the dawn of time BACKBONE.* and BACKSTAT.* The IRNROUTE file is not such, it doesnt even mention the Z1B, then again, the SLA doesnt mention the Z1B publishing a route file. All this means is you all can take any file of any type, vote to declare it one of your info files, even if it isnt and wallah. How about your autoexec.nt being declared a Z1B info file, all you got to do is put it up for a vote? DR> Files % Hatching - any recognized DR> Fidonet backbone % may DR> hatch in this area. This is not in dispute, nor has it ever been for the normal fare for any backbone file which contains the usual list of info such as tag names, added or dropped echoes ad naseum. DR> A routing chart is an information file. DR> We consider IRNROUTE to be information that we use. So what, your washing machine is something you use, that doesnt mean everyone wants or needs _your_ washing machine? Mine works fine thank you. DR> Since according DR> to DR> our SLA routing NetMail is something that a Z1B Hub must do. DR> We use our portion of BACKBONE to move that file. Not everyone is bound by _your_ sla. DR> There are no control tactics by the Z1B. The area is partly ours to DR> hatch in. If a person cant opt out of the file it is control tactics, I posted numbers that indicate that not everyone needs/wants a routelist, why is that? DR> The only control tactics being used here are by the NAB and Janis so DR> please get your facts straight here. Chicken little had a saying................. >> What they are doing amounts to file echo hijacking, pure and simple; >> and it is a reprehensible act. DR> You cannot hijack something that is already partly yours. But if you are putting out something they want and something they dont want, why not offer a choice? >> And I suppose now that those in the Z1B would *like* file echo >> hijacking to become commonplace? How about if someone suddenly >> decides to start hatching MP3's in the Z1_REC echo? It's the /exact/ >> same thing that they are doing. DR> Someone can only be an REC. If the RECs decide that is how they want DR> to use that area, they have EVERY right do so. If that someone is not DR> an REC then their uplink should NOT have their access set to where DR> they can hatch into the area. Problem is in the fervor to create your list, you merely selected an area to have the most exposure for your list.. You created it with good intentions but are distributing it with bad ones.. == Ross http://www.the-estar.com:8080 ross@the-estar.com or rcassell@home.com ICQ = 5305939 --- GoldED/W32 3.0.1 * Origin: The Eastern Star [Mail Hub] - 864.573.7069 (1:18/500) .