asciilifeform: (tcp, that massive barrel of liquishit, was designed before the discovery of luby code - or any of the subsequent 'fountain' algos)

asciilifeform: $s fountain code

asciilifeform: artifexd: you don't strictly speaking need fountain code in first version of this apparatus.

asciilifeform: artifexd: there are several known ways of doing a 'fountain code' (term of art) - where a bitstring, B, is transformed into a number, N, of shorter bitstrings, whereby X of N can be collected, in any order, and with certain quantity of errors permissible, to reconstitute B.

asciilifeform: at any rate, tiny packets plus fountain code plus each one is signed, will work great with transmission media other than internet (say, shortwave)

asciilifeform: what follows is the payload, divided into K gibblets, each below udp mtu in size, each signed with ephemeral key. the gibblets are coded using fountain code (e.g. 'raptor') and you need N of K - in any order - to reassemble. ☟︎

asciilifeform: someone probably wonders 'wtf, why fountain code'. answer: getting rid of tcp.

asciilifeform: i may have spoken of this once. i've a very rough draft of precisely this, using an interesting bit of mathematics called 'fountain code'