Subj : TITHmailer
To   : deon
From : Deuce
Date : Mon Nov 17 2025 14:49:58

  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

.