No description
Find a file
jvanvik 065c922287 Server-run play, part 2: the engine
The engine that runs every network of a server session (server-sim design,
section 4): each network in its own vm realm, realms in a small pool of
worker threads, a promise API for the session host. Nothing uses it yet;
the plain build and the game are unchanged (no file under src/).

- scripts/lib/mp-sim-realm.js: one network in a DONT_CONTEXTIFY realm
  running the plain page's game (never the MP page's client folder), with
  recording DOM stand-ins, no-op timers that count, and the srv... calls:
  load from a checkpoint (route memory seeded, then routed), begin a new
  network, marks and restores, the day as a page runs it, the action
  pipeline with drafts, arming, the sanitize gate and rollback, what-ifs
  that put S, R, the dice and uidN back, pulls with top-level key diffs,
  slim R and flow records on demand, fx captured and bounded, saves, cards.
- scripts/lib/mp-sim-worker.js: realms per session in one worker, days one
  network at a time with other messages between them, loads and unloads
  waiting for a session's day, time limits; a throw goes back to the mark
  in place, a timeout gets a fresh realm (new epoch) carrying the old R, a
  day is retried once and the network broken after a second failure.
- scripts/lib/mp-sim-engine.js: createEngine() with the fake engine's API,
  placement by realm count, every pending call rejected when its worker
  exits, a worker of its own after two exits in an hour; snapWith() joins
  the host's clock, roster and since to a realm's snapshot.
- Contract: a pulled snapshot is the realm's half (the host adds clock,
  roster, since); haptic fx carry milliseconds; the fake engine follows,
  with close() and snapWith(). The button crawl moved to tests/lib.
- Tests: realm vs jsdom byte for byte over 60 scenic big-network days with
  actions; restore; retry after a throw or a timeout; realm order; a timer
  audit and the gate over a sweep of sent buttons (SIM_LONG=1: a year and
  every button); captures, rollbacks, asks, selection reports, ordering,
  bounds, pollution, worker exits; the act tables against the game.

The gate found two keys the game writes in a shape a reload repairs (buyTE's
S.te, mkLeave's S.monkey): game fixes for the integrator, kept visible as a
todo test and a list in the audit.

Rebased onto the 3.3.0 merge (61e31c5): the engine itself needed no change. A
realm still routes in the game's own code (no route worker, no saves), the
route cache that now keeps list orders from day to day leaves a checkpoint and a
retry the same, and the capacity market and moved customers play in a realm as
on a page, under the strict gate. The tests needed three things: an old save's
first days earn the new traffic badges, which the unwatched network's snapshot
keeps; the restore test compares JSON text with sorted keys instead of a
deep-equal of two networks (a diff of gigabytes when they differ); and the crawl
opens the windows that move a customer, with a new test playing the market's and
the path moves' acts, 40 days of sales and a checkpoint against the page.
2026-11-09 19:30:38 +01:00
.claude/skills Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
.github Clear the open code scanning alerts 2026-11-09 12:36:08 +00:00
docker Container image: releases only, a token by default, lean layers; every action pinned 2026-11-05 20:14:04 +01:00
docs Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
scripts Server-run play, part 2: the engine 2026-11-09 19:30:38 +01:00
site Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
src Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
tests Server-run play, part 2: the engine 2026-11-09 19:30:38 +01:00
.dockerignore Container image: releases only, a token by default, lean layers; every action pinned 2026-11-05 20:14:04 +01:00
.gitattributes Docs and guard rails: GitHub Pages only, where code goes, updated skills 2026-10-27 10:15:12 +01:00
.gitignore Multiplayer for self-hosted copies: sessions, server-side saves, a leaderboard 2026-11-07 00:42:39 +01:00
CHANGELOG.md Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
CLAUDE.md Agent mode: an AI agent plays in the player's own tab, with the agent's clock or a running one 2026-11-03 16:18:43 -05:00
CODE_OF_CONDUCT.md Code of conduct: jokes target networks, cables and routers 2026-10-31 13:24:36 +01:00
CONTRIBUTING.md README: add star history, drop Releasing, Hosting setup and Analytics; Signal is for chat, issues for anything meaningful 2026-10-27 18:26:07 +01:00
LICENSE Add MIT license, contributing guide, CLAUDE.md, architecture notes and repo skills 2026-10-25 07:07:00 +01:00
package-lock.json Move customers between paths, and big networks route in half the time (3.3.0) 2026-11-09 13:37:12 +00:00
package.json Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
README.md Agent mode: an AI agent plays in the player's own tab, with the agent's clock or a running one 2026-11-03 16:18:43 -05:00

Series of Tubes

Build the internet, one tube at a time. A free cartoon browser game about how the internet really works. Play it at seriesoftub.es.

Series of Tubes

You start with one router in one city and grow into a transit-free Tier 1:

  • Customers: home broadband ("eyeballs"), enterprises, hosting, L2VPNs, DDoS protection, high-frequency traders with latency budgets, AI GPU data centers and hyperscaler DCI deals. Some come with very specific requirements.
  • Interconnection: IP transit billed on the 95th percentile, internet exchanges with route servers, open/selective/restrictive/paid peering, PNIs, embedded CDN caches, and NNI fabrics for virtual circuits and remote peering.
  • Infrastructure: leased waves on around 40 subsea cable systems modelled on real ones, dark fiber (leased or self-built) lit with DWDM and ZR+ optics, router generations that cap your port speeds, and LAGs to bundle ports when one isn't enough.
  • Traffic engineering: see exactly what fills each link, tune link metrics and egress preferences, and route traders over the fastest path and backups the scenic way.
  • Things break, constantly: backhoes, sharks, fat fingers, route leaks, RPKI mishaps, DDoS, cooling failures, Red Sea and Baltic cable cuts, sanctions and sovereign internet drills.

Every company is a pun. No real company names are used.

Learn how it really works

This game simplifies a lot, and gets some things gloriously wrong on purpose. For the real thing, go to How the Internet Works by Thomas Kjær Aabo (source): an interactive, zoomable map that follows your data from Wi-Fi and copper to undersea fiber, as the internet works today, in 2010 and in 1995, with simple or technical explanations. If you enjoy Series of Tubes, you will learn more from an hour there than from a year of laying cartoon fiber here.

Playing locally

It is a single static page, assembled from the files in src/ by a small Node script:

npm ci
npm run dev                   # http://localhost:8080

Progress is saved in your browser's local storage.

The game speaks English, Italian, Portuguese, French, Spanish and German. It follows your browser's language the first time and remembers the one you pick under Settings or on the title screen.

Development

npm ci
npm run dev    # development server on localhost (--host to share): assembles src/ on every request, reloads on save
npm test       # headless tests: boot, geography, a year of play, every incident, every panel
npm run build  # writes the site for GitHub Pages to _site/, with version and date stamped in
npm run i18n:check  # lists text missing from (or stale in) the translations
npm run mcp    # the game as an MCP server, so an AI client can play and debug it, headless or in your tab (docs/MCP.md)

Community

Come hang out in the Series of Tubes Signal group. Share screenshots of your network, suggest cities, and argue about peering policy with other players. There are fewer backhoes there than in the real thing.

Signal is for chatting. Bugs, feature requests and anything else that should not get lost go into a GitHub issue.

Star history

Star history of Series of Tubes

Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md. Everyone taking part follows the Code of Conduct: be excellent to each other.

License

MIT © 2026 Frederic Jung