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,429 of 43,341    |
|    Digital Man to Gamgee    |
|    Re: Badareas.lst location    |
|    25 Sep 25 13:35:11    |
      TZUTC: -0700       MSGID: 54954.sync@1:103/705 2d3bb429       REPLY: 54953.sync@1:103/705 2d3b9df0       PID: Synchronet 3.21a-Linux master/38be34386 Sep 22 2025 GCC 12.2.0       TID: SBBSecho 3.29-Linux master/38be34386 Sep 22 2025 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       FORMAT: flowed       NOTE: FSEditor.js v1.105        Re: Re: Badareas.lst location        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.              If a sysop had multiple sbbsecho config files and they all used the default       badareas.lst file path (which seems unlikely), then the sysop would not need       to type in a new value if/when importing that badareas.lst file into SCFG. I       only mentioned the sbbsecho.ini file issue because it means that       desired/expected behavior is that the bad area file path is pulled from that       file automatically, but there's really no way for SCFG to know what sbbsecho       config file path/filename that SBBSecho is *actually* using.                      > 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?              Yes.               > Or will it always go to ../data ?              No, the path/filename set in sbbsecho.ini is what SBBSecho (or at least the       instance that runs with that config file) will update/write when messages for       bad area-tags are received.       --         digital man (rob)              Synchronet "Real Fact" #113:       Weedpuller "Assassin" http://youtu.be/opw9RPUOcv8       Norco, CA WX: 80.5øF, 50.0% humidity, 6 mph WNW wind, 0.00 inches rain/24hrs       --- SBBSecho 3.29-Linux        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 19/25 33 41 105/81 106/201 987 124/5016 128/187 129/14 130/330       SEEN-BY: 153/7715 154/110 218/700 226/30 227/114 229/110 206 317 400       SEEN-BY: 229/426 428 470 700 705 266/512 280/464 291/111 320/219 322/757       SEEN-BY: 342/200 387/18 25 396/45 460/58 633/280 712/848 902/26 5075/35       PATH: 103/705 280/464 396/45 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca