[Hydrocarb0n]

The File Transfer Service utilizes the quic-go implementation of the quic Protocol, built on top of UDP. Since quic allows for multiplexing of streams on a single connection, the service takes advantage of this to attempt to speed up file transfers by processing and writing the file from the remote host (the server) to the destination (the client) concurrently

[01HNNWZ0MV43FF]

That's clever. I'd wondered how you can transfer files with "any order, as long as the entire file completes as fast as possible" semantics, that is, without head-of-line blocking, without incurring a lot of overhead. I guess the answer is to use lots of big chunks and lots of streams, instead of lots of tiny packet-sized chunks in 1 stream.

[adgjlsfhk1]

it's exactly the way torrents have worked for decades, so it's pretty well tested.