Subj : Re: Is binkp/d's security model kaputt?
To   : tenser
From : Avon
Date : Sat Sep 04 2021 07:55 pm

On 04 Sep 2021 at 03:24a, tenser pondered and said...
 
 te> seem scalable.  USENET solved this by including a routing path as
 te> articles transited the network; this mean that one could cheaply
 te> detect loops when communicating with peers.

Yes this is a good system. Like the bang paths of UUCP days.

 te> I thought about these problems a bit when I wrote ginko, and became
 te> convinced that the real solution was to serve legacy systems at the
 te> edge.  For backbones and hubs, use new formats with a standard
 te> canonicalization and checksumming for duplicate detection and article
 te> identification, but only translate to/from legacy formats when
 te> communication with legacy software.

I recall you working on Ginko and we doing some tests some years back to get
compatibility with legacy FTN stuff :) I agree with your comments above.

I think when it comes to discussions such as these whereby folks are keen to
innovate the inevitable tensions arise between the boundless opportunities of
innovation without hindrance of being tied to legacy systems / ways of doing
/ dogma etc. vs. wanting some way for those very same legacy systems to be
able to take part if they wish.

 te> Honestly? The whole hunk of poo ought to be tossed and re-architected.
 te> Using the things we've improved on in the last 40 years will actually
 te> simplify the whole mess, making it easier to move to IoT devices and
 te> so on.

:)

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.