Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNCHRONET    |    Rob Swindell fetishistic worship forum    |    43,341 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 42,430 of 43,341    |
|    Gamgee to Digital Man    |
|    Re: Badareas.lst location    |
|    25 Sep 25 16:21:45    |
      TZUTC: -0500       MSGID: 54955.sync@1:103/705 2d3bc820       REPLY: 54954.sync@1:103/705 2d3bb429       PID: Synchronet 3.21a-Linux master/955e50fea Aug 10 2025 GCC 14.2.0       TID: SBBSecho 3.29-Linux master/38be34386 Sep 22 2025 GCC 12.2.0       BBSID: PALANTIR       CHRS: CP437 2       FORMAT: flowed       -=> Digital Man wrote to Gamgee <=-               DM> Re: Re: Badareas.lst location        DM> By: Gamgee to Digital Man on Thu Sep 25 2025 01:51 pm               > DM> Yes in theory, SCFG could read the sbbsecho.ini file to find whatever        > DM> path/filename the sysop chose to name that file. However, a sysop can        > DM> create/use multiple sbbsecho configuration files (they don't have to be        > DM> ctrl/sbbsecho.ini), so SCFG wouldn't magically know how to find any        > DM> other non-default SBBSecho config files.               > That seems a pretty niche use-case - I'd guess that VERY few sysops are        > using multiple sbbsecho.ini files. If somebody *was*, then yes I could        > see how they might need to type in a new value in the input dialog to        > import that badareas.lst into SCFG. But for the other 99% ...? To be        > fair - I see ZERO reason to change it from the default location anyway.               DM> If a sysop had multiple sbbsecho config files and they all used the        DM> default badareas.lst file path (which seems unlikely), then the sysop        DM> would not need to type in a new value if/when importing that        DM> badareas.lst file into SCFG. I only mentioned the sbbsecho.ini file        DM> issue because it means that desired/expected behavior is that the bad        DM> area file path is pulled from that file automatically, but there's        DM> really no way for SCFG to know what sbbsecho config file path/filename        DM> that SBBSecho is *actually* using.              Okay, understood, thanks.               > I guess my question then is - does the location specified in        > sbbsecho.ini for the badareas.lst file actually make that file get        > created/updated in the location specified?               DM> Yes.              Roger that.               > Or will it always go to ../data ?               DM> No, the path/filename set in sbbsecho.ini is what SBBSecho (or at least        DM> the instance that runs with that config file) will update/write when        DM> messages for bad area-tags are received.              Very good, thank you for the explanation/clarification.                            ... Gone crazy, be back later, please leave message.       --- MultiMail/Linux v0.52        þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 4/0 88/0 90/0 93/1 103/705 105/81 106/201 124/5016 128/187       SEEN-BY: 129/14 153/757 7715 154/10 30 110 203/0 218/700 221/0 6 226/30       SEEN-BY: 227/114 229/110 206 317 400 426 428 470 700 705 240/1120       SEEN-BY: 240/5832 263/1 266/512 280/464 5003 5006 291/111 292/8125       SEEN-BY: 301/1 310/31 320/219 322/757 341/66 200 234 342/200 396/45       SEEN-BY: 423/120 460/58 467/888 633/280 712/848 770/1 900/0 102 106       SEEN-BY: 902/0 19 26 904/13 905/0 5019/40 5020/400 5075/35       PATH: 103/705 280/464 341/66 902/26 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca