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 48,173 of 49,116    |
|    Deuce to deon    |
|    src/tith/standards/TSP-0001.txt    |
|    28 Nov 25 22:34:47    |
      TZUTC: 0000       MSGID: 53591.syncprog@1:103/705 2d902b05       REPLY: 15670.dove-syncprog@12:1/2 2d8e8225       PID: Synchronet 3.21a-FreeBSD master/1c123cf4a Oct 24 2025 Clang 19.1.7       TID: SBBSecho 3.32-Linux master/ec8f7009f Nov 15 2025 GCC 12.2.0       BBSID: BBSDEV       CHRS: CP437 2       FORMAT: flowed       NOTE: FSEditor.js v1.105        Re: src/tith/standards/TSP-0001.txt        By: deon to Deuce on Fri Nov 28 2025 01:54 pm               > If it was the other way, then it could be delegated to the system in        > question. IE: The nodelist for the domain (and addresses) are with the ZC,        > but the details come from the end system.              Yeah, that seems like a really weird way to delegate. :D               > EG: if _tith.f2.n2.z885.bbsdev.net was delegated to my BBS, then the answer        > to _sysop._tith... _systemname._tith... could come from the BBS        > software/system in question and be consistent with what the BBS software        > uses (binkp) when interacting with other systems (instead of potentially        > being different to whats in the "nodelist").        >        > Probably a stretch to implement - but just an idea :)              Yeah, I've switched from _tith_sysopname to _tith-sysopname to make it more       clear that they're not separate components. The sysopname specifically I       expect to use as the "To" user for status messages, so I do need that, and the       iflags is pretty obvious why it's needed.              I expect to come up with reasons to need a couple other fields (system flags       for example for non-ICM nodes) but have no immediate plans to implement them.       ---        þ Synchronet þ The future of BBSing        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 10/0 1 13/0 102/401 103/705 105/81 106/201 124/5016 128/187       SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 700 810 226/30       SEEN-BY: 227/114 229/110 206 317 400 426 428 470 700 705 266/512 280/464       SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280       SEEN-BY: 712/848 902/26 5075/35       PATH: 103/705 218/700 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca