TZUTC: 0000   
   MSGID: 53559.syncprog@1:103/705 2d813d7e   
   REPLY: 15633.dove-syncprog@12:1/2 2d7fb220   
   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: TITHmailer   
     By: deon to Deuce on Mon Nov 17 2025 08:15 am   
      
    > I like the way you plan on handling new payloads, and had not thought about   
    > it that way for what I'm working on. I should have considered it, since I'm   
    > processing media files and they use a similiar approach for media atoms.   
      
   Yeah, a lot of where FTN ended up is just inertia.  There's various proposals   
   from the 80s and 90s rotting away suggesting similar things, but they never   
   caught on in FidoNet, so most of them are half-baked at best.   
      
   It's been an interesting journey even for just the small bit I've done so far,   
   realizing that the point I was starting at wasn't quite right... pretty sure   
   the first thing I'll be creating now will be the bundler, which will be the   
   thing that implements the Binkley-style outbound, then the unbundler, which   
   will implement the inbound, THEN the mailer.   
      
   With those three things in place, it should be possible to convince Synchronet   
   with SBBSecho to do full 5D support using multiple sbbsecho.ini files.  Once   
   that's working, I'll define the message format and replace SBBSecho.  After   
   that it's just a matter of fleshing out all the various maintenance robots,   
   nodefix, filefix, areafix, etc.   
      
   The assumption of default direct has some interesting implications for   
   echomail that I'm still working through, it still keeps collapsing into a   
   simple star topology, which means the SEEN-BY for pretty much every post will   
   either be only two nodes, or a copy of the whole nodelist.  It feels like just   
   a usable PATH will do the job, and a robust MSGID will allow loops to be   
   detected and mitigated/fixed.   
   ---   
    þ Synchronet þ The future of BBSing   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715   
   SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110   
   SEEN-BY: 229/206 317 400 426 428 470 700 705 240/1120 5832 263/1 266/512   
   SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 633/267 280 384   
   SEEN-BY: 633/414 418 420 422 2744 712/848 770/1 902/26 5020/400 5075/35   
   PATH: 103/705 280/464 633/280 229/426