Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_PROGRAMMING    |    Synchronet/Baja/XSDK Programming    |    49,116 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 47,044 of 49,116    |
|    Rob Swindell (on Windows 11) to Git commit to main/sbbs/master    |
|    src/sbbs3/ftpsrvr.c mailsrvr.c main.cpp     |
|    02 Jul 25 17:25:44    |
      TZUTC: -0700       MSGID: 52435.syncprog@1:103/705 2ccbd0db       PID: Synchronet 3.21a-Linux master/a43ca30ea Jun 18 2025 GCC 12.2.0       TID: SBBSecho 3.28-Linux master/9534d63a7 Jul 02 2025 GCC 12.2.0       BBSID: VERT       CHRS: ASCII 1       FORMAT: flowed       https://gitlab.synchro.net/main/sbbs/-/commit/1ec7cb53a8f52df12d6623e7       Modified Files:        src/sbbs3/ftpsrvr.c mailsrvr.c main.cpp services.c trash.c trash.h websrvr.c       Log Message:       Support a filter (*.can) file 'quiet' attribute (e.g. "q=1")              A dubious feature. This will squelch any "CLIENT BLOCKED" type log messages       assocated with a filtered client. Importantly, other log messages related to       the client connection won't be (can't be) squelched, so this isn't going to       really be a useful feature in my opinion, but when sysops ask for this (e.g.       silently-blocking specific hostnames), I want to be able to demonstrate why       that's not really practical.              The syntax is " |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca