No description
Find a file
Antoine 351b3aa522
WebGL map: take a lost context back, and let it go for Always 2D
The first loss of the WebGL context gave the card up for the session. A context can come back (a driver reset; on a
phone, sometimes just leaving the app), so a phone that went to another app came back to the slower 2D map until the
page was reloaded. Always 2D, chosen in Settings, kept the context and its 64 MB atlas for a map drawn in 2D.

A loss now leaves the 2D map drawing while the context is away (glLost(): the event is cancelled so the browser may
give it back), and everything on the card is built again on the same context when it comes back (glRestored(),
glForget(): glInit() runs as for the first frame). A card lost more than GL_LOSSES (2) times is given up for the
session, so a card that keeps failing does not keep the map switching. Always 2D lets the context go through
WEBGL_lose_context and Auto asks for it back, the same path, never counted as a loss; a context the browser gives back
after the player chose Always 2D is let go again. Without the extension, and for the GPU benchmark's switches
(mapGl(on,false)), the context is kept as before. The listeners and the overlay's wrappers are set once.

Diagnostic info says when the map waits for a lost context. Tests: webgl-context-restore (7), and the loss test of
webgl-out-of-memory now waits for the context instead of giving it up.
2026-11-05 00:21:35 +01:00
.claude/skills Release skill: CI tests and benchmarks a release, so don't run them locally 2026-11-04 09:31:25 +00:00
.github CI: tests in four parts on four runners, every core in use, older PR runs cancelled 2026-10-31 14:11:02 +01:00
docs Draw the map with WebGL2 by default, with the 2D canvas as fallback 2026-11-04 22:37:12 +01:00
scripts WebGL map: keep the 2D map where WebGL is drawn by the processor 2026-11-04 22:37:13 +01:00
site Settings: one Diagnostic info readout for the screen, the map's drawing and its speed 2026-11-04 22:37:15 +01:00
src WebGL map: take a lost context back, and let it go for Always 2D 2026-11-05 00:21:35 +01:00
tests WebGL map: take a lost context back, and let it go for Always 2D 2026-11-05 00:21:35 +01:00
.gitattributes Docs and guard rails: GitHub Pages only, where code goes, updated skills 2026-10-27 10:15:12 +01:00
.gitignore Series of Tubes 1.0.0 2026-10-23 09:01:39 +02:00
CHANGELOG.md 2D map: keep the land picture on the graphics card in Firefox on a computer 2026-11-04 22:37:15 +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 Kinder jokes, meetings where they meet, a quiet North Korea (2.9.1) 2026-11-04 16:40:38 +01:00
package.json Draw the map with WebGL2 by default, with the 2D canvas as fallback 2026-11-04 22:37:12 +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