Board:   [fsxNet] BBS Software Development/Support
Subject: Re: x/84 revived
From:    deon (21:2/116)
Date:    Wed Oct 21, 2026 08:59

  Re: Re: x/84 revived
  By: Randers to deon on Wed Oct 21 2026 09:34 am

Howdy,

 > Fair enough. I've long wondered how much upkeep is needed for Clrg. And how
 > long it took to get it going in the firtst place. The upkeep is probably
 > never ending, like all this stuff, I suppose. But hopefully never
 > overwhelming. Thanks for explaining it, one less glitch at my end to
 > inspect.

Actually, not much upkeep at all - although I'm always "optimising" things, when inevidently breaks something.

I'm working on about 3 or 4 things at the moment, and depending on my energy levels will determine if I work on clrghouz or something else. I've often let clrghouz run for months without looking at it.

That said, I'm playing with TITH, Ive been toying with a few different packet formats and transfer methods since the current ones I need to work around to get them to work the way I want. I'm liking TITH, its good getting another idea from somebody else, that skins this cat a different way, and I think it is way better than anything I've been thinking.

I plan to make it available soon, it'll suit my first requirement of a clrghouz <==> clrghouz transfer and then see how to get it out there for other mailers.

If anybody is curios, its here: https://github.com/RealDeuce/tith

In simple terms, its public key (libhydrogen) related, so no session, no packet, no areafix passwords, you use the same public key for all networks - and the public key could be in DNS or a nodelist.

And data transfers are TLV encoded, so no ambiguity about componets of a message, eg: kludges in the middle of message text, no corrupt packets, etc :)


....δεσ∩
--- SBBSecho 3.37-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
.