[330 stars] AirPipe v4.4: True p2p file transfers from anywhere to anywhere

Third time posting AirPipe here. If you missed the earlier posts: airpipe send file.pdf prints a QR code in your terminal. Scan it with your phone, or type the passphrase on any device, and the file moves peer to peer over WebRTC with a relay fallback for hostile NATs. Everything is encrypted before it leaves the device and the key travels in the URL fragment, so the relay only ever sees ciphertext. Server to phone, phone to laptop, no accounts anywhere. New in v4.4: AIRPIPE_MINIMAL_UI=true serves a plain send/receive page at / and nothing else. Someone here said, fairly, that a self-hosted relay shouldn't serve my project website as its homepage lol. /metrics and the live stats in /health went private by default. Set AIRPIPE_PUBLIC_STATS=true to expose them again. Rate limiting stopped trusting X-Forwarded-For from strangers. If your relay sits behind a tunnel or reverse proxy, set AIRPIPE_TRUST_PROXY_HEADERS=true . Since the May post it also picked up multi-file sends: several files, one passphrase, they land as one bundle. There are Windows binaries and a multi-arch Docker image now, plus a Homebrew tap ( brew install sanyam-g/airpipe/airpipe ). Self-hosting the relay is one container: docker run -p 8080:8080 ghcr.io/sanyam-g/airpipe-relay Repo (MIT, 338 stars now, a lot of them from this sub): github.com/Sanyam-G/Airpipe Try it on the hosted relay first: airpipe.sanyamgarg.com I am Sanyam, a college student. Here is my portfolio/resume: sanyamgarg.com