Under the hood

The articles

1. 01

   Architecture: control and file data are separate

   A transfer has two jobs: decide who may send what to whom, and move the encrypted bytes. pipeit keeps them apart.

2. 02

   From sending to verified receipt

   The factual order of an online transfer: order, acceptance, encrypted frames, verification and a signed receipt.

3. 03

   Encryption: file content, keys and signatures

   Which standard algorithms protect a file sent from device to device, what each one does, and what the profile does not promise.

4. 04

   Connectivity: nearby, WebRTC, TLS, routing and ICMP

   How devices find each other nearby and across networks, why a routed network needs no special format and what the ICMP path for locked-down Linux hosts does.

5. 05

   Relay: diskless does not mean workless

   Why the relay (server route) keeps no file yet still uses memory and CPU, and how backpressure keeps it bounded.

6. 06

   Streaming and the send window: throughput without an infinite buffer

   Four sizes that must not be confused, how a window lets a long link stay busy, and why a bigger window alone makes nothing faster.

7. 07

   Resuming: acknowledgement, checkpoint and receipt are different

   Five signals that sound alike and mean different things, and what resuming actually keeps.

8. 08

   Folder streams and safe target directories

   How a native folder is sent without a full archive, what the receiver checks and why the modes differ.

9. 09

   Authentication and MCP: signing in is not a file key

   Account session, device identity and MCP consent are three different things; here is how they fit together.

These articles explain how pipeit works. Sizes, windows and time limits are implementation values that can change; they are not promises of speed or capacity. Nothing here is an external security audit.