The video series · shot and edited
Eight videos, one path — from nothing to a working call.
The on-ramp is sequential: install to call. Every video keeps its honesty beat — the thing that failed on camera stays in. And the numbers on camera go lower than the hero's: the ladder demo bottoms out at 164 Kbps, 160×120, audio holding, no dropped frames, then climbs back.
"Not the right way, not the only way — I submit it as a first implementation." — video 2
Install to call, in eight steps.
Root cause, instrument, prove — and where FrogNet came from.
The habits first, then the origin arc. Memory, not messages; the assembler-to-C argument; a live monitor across four machines. The 850 Kbps call is stated and immediately undercut: it is high, and you will do it at 450 and maybe lower.
A standalone, autonomous mesh — every FrogNet identical.
A 254-address segment per node, no permanent external control plane, and the sentence that sets the epistemic posture of the whole project: not the right way, not the only way — a first implementation. Then the Guild.
What must be hardware, and what only must be software.
Debian. A Pi 4 with 2 GB is enough. An AP-mode router is required, and the one real restriction is stated plainly: we provide DHCP for the projected network.
frognet_install, the prompts, and the pond.
frognet_install, the --preserve flag, the broker prompts, setup_lillypad, reboot.
http://<host>:<port> — choose http, and leave the URL path empty. See the broker installation video for instructions on setting up a broker machine.First boot: routes appear, and the node is on the network.
run_merge, routes appearing live, a ping to New York, the node back online, and the same sensor record read from two machines.
The broker joins two independent FrogNets.
The bundle and its build script, frognet-pond create/list/status, and /etc/frognet/tunnel.conf. A rendezvous, not an authority — and a dependency at join time, which is said out loud.
Watching the pond think.
Each machine writes its own state; the monitor just reads it — the same record from two viewpoints, and a live degraded peer diagnosed on camera. Its provenance is SCCM and OSTC.
The ladder, on camera.
Bundles; the media, board-game and database hosts set at each merge; then the ladder demo — 1080 refused, 720 held, 854×480, 640×360, 480×360, 320×240, 160×120, and the climb back. Roughly four seconds down, fifteen up: the asymmetry is deliberate.
Watched by choice, after the on-ramp. Not prerequisites.
Where several routes lead into one topic, one is marked start here and the rest go deeper — semantic compression especially. They are not five consecutive prerequisites.
How a node finds neighbours and installs routes.
Then More Discovery goes deeper: the recursive who-do-you-know expansion, route selection, convergence, and service-host selection.
The intercept, the permanent socket, the byte accounting.
Live journalctl: a 21-byte SAME and a 31-byte reconstructed DIFF, with the accounting on screen.
BLDC-1 and FNWP-1, with live measurements.
The current canonical recording; earlier semantic-compression videos are superseded. It runs the same pipe_workload benchmark as Proxy and Daemon — watch this one first and go to Proxy and Daemon for the plumbing; you need not sit through the benchmark twice.
Registering your own wire protocol in two functions.
Goes deeper on the compression path from the application side.
Where the moving authority comes from.
The elected role behind FrogNet Memory. It floats, and it holds no durable state.
Linda, 1985 — addressing memory by three keys.
Then Tuples and REST (part 2) goes deeper: the tables, api.php, the backgammon case. Memory Backing Store opens MySQL and shows where the bytes actually live.
Attack the mechanics under arbitrary topologies.
The falsification instrument. Bring an oracle.
The surface, named honestly.
One port must answer — here is the host, here is the port. The security page →
Insertion into a brownfield enterprise.
Below actual egress; unmodified hosts participate. The enterprise page →
Not part of the on-ramp — where you look afterward.
Pairs with Croakus ch. 53b, which was written from it.
"C didn't replace assembler. It uses assembler. You lose some of that exquisite control, and you gain so much more. That's what FrogNet Memory does for you."
The Monitor video — the best statement of the thesis in the series
Don't choose among twenty-five videos. Choose a question.
Installation → First Run → the 900 MHz proofs → Communicator degradation → Dan's lamp. The evidence page →
Discovery → Proxy and Daemon → Semantic Compression → DatabaseHost → Memory and Tuples → Communicator.
Simulator → the Croakus → handler and programming examples → the Guild. The seats →
Existing Networks → Croakus §1b and §22b → Security → contact. You insert it, not migrate to it →