TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 6137144f   
   REPLY: 1:153/757.21@fidonet f4270c54   
      
   Hi August,   
      
   On 2021-09-05 21:32:00, you wrote to me:   
      
    AA>>> and [3] gets a spot in a .NA file that is distributed to   
    AA>>> boards everywhere.   
      
    WvV>> It's only in the .na file that is distributed in the   
    WvV>> monthly elist*.zip file. I very much doubt anyone   
    WvV>> processes it automatically and have areas auto created   
    WvV>> and destroyed.   
      
    AA> When I ran my bbs, the .NA file served as a fine catalog of   
    AA> what was available out there.   
      
   Probably the one distributed by the NAB...   
      
    AA> But with a little more awareness, sysops can be given the   
    AA> heads-up that elist*.zip is a fine goto package to see what   
    AA> echos are yearning to be linked up.   
      
   The elist*.zip is mostly a mausoleum of dead areas. With totally inaccurate   
   Volume information... :-/   
      
    WvV>> An elist entry doesn't mean the area exists.   
      
    WvV>> An entry in the NAB's list, means it at least exists on   
    WvV>> the NAB.   
      
    AA> Ya. Ok. Once again, you nabbed me on a technical issue. But I   
    AA> am trying to describe a practical convenient system that works   
    AA> 24/7 using the computers that people love to see doing the   
    AA> things that they were designed for: automation.   
      
   If you want accurate/reliable information of what is available for you, you   
   should consult the %LIST of your links.   
      
    AA> An announcement via the elist-bot system doesn't "create" the   
    AA> echo, but it is an easy way to get the word around,   
      
   There aren't many nodes that consistantly scan the list for changes between   
   updates.   
      
   If you want a new area to get known and linked to, you will have to announce   
   it manually in selected echomail areas, that is the only way.   
      
    AA> and the contents are presented in a consistent readible way with all   
    AA> info contained within.  Instead of a long series of public or pm   
    AA> messages back and forth, everything any sysop needs to know about a   
    AA> potential echo seeking distribution is contained in the elist system   
    AA> of files.   
      
   Not really, you still need to PM your links, to get them to connect to it.   
      
    AA>>> ..But the initial elist-bot process is something anyone   
    AA>>> could do to get something started at their convenience.   
      
    WvV>> You could see it as a problem to. If anyone can create a   
    WvV>> listing for any area, existing or not.   
      
    AA> Everything has potential to be abused.   
      
   It has been in the past.   
      
    AA> But talking successfully to the elist-bot provides some assurance that   
    AA> the creator/ moderator is serious.  I doubt that a creator and   
    AA> potential moderator would want to go through all the trouble of   
    AA> following the elist language just to be painted as a nuisance.   
      
   Some did in the past... But we already knew they were a nuisance. :-/   
      
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 103/705 105/81 124/5016 129/305 153/757 203/0 218/840 221/0   
   SEEN-BY: 221/1 6 360 229/426 428 664 700 240/5832 280/464 282/1038   
   SEEN-BY: 292/8125 301/1 310/31 322/757 335/364 396/45 423/81 120 460/58   
   SEEN-BY: 770/1 4500/1   
   PATH: 280/464 221/1 6 229/664 426