draw() asked dfCap() three to five times per fiber link and per frame (width,
colour, label, up or down), each time over all its channels: on a save with
3,140 dark fibers of 18 channels on average that was about half of draw()'s
JavaScript. dfCap() now keeps its answers in DFC while one frame is drawn
(cleared in a finally, so a failed frame keeps nothing), and the link label is
built once per line instead of once per world copy. Links entirely above or
below the screen are skipped like those left or right of it already were.
Player save (202 POPs, 3,142 links), jsdom: draw() 40 -> 25 ms; perf-bench
"Map at three zoom levels" 89.7 -> 47.1 ms. Canvas call log identical at
every zoom without the vertical skip; Firefox pixels identical (SHA-1 of the
canvas) in 7 views. Firefox still spends ~95% of the frame painting.
compute(), the daily mood check and new alien-wave/fiber-pair offers asked
S.links.find() or S.biz.filter() once per customer or per link. On a save
with 2,950 links and 18,000 customers (16,000 alien waves) that was ~150 ms
per compute, ~250 ms more per day, and ~650 ms when a wave offer spawned.
linkIds() and fiberUse() build the lookups in one pass; fiberOk, bizSf,
soldSlots, freeCh and pairFree take them optionally, and give the same
answers as before (first link with the id wins, sums in S.biz order).
Player save (202 POPs, 2,958 links, 17,967 customers), median of 15:
compute 323 -> 124 ms, dayTick 545 -> 133 ms, after 356 -> 149 ms.
Big-network fixture: unchanged. Routing results identical to main.
Covers GitHub, the Signal group and anywhere the project is represented.
Reports go to Frederic privately on Signal. Linked from the README and
CONTRIBUTING.
The build swaps every label for a short id in the shipped page, the inlined
English and the translation files (scripts/lib/compile-labels.js). Labels
passed to N_() stay whole because saves keep them. Against 1.33: page +4%
gzipped (321 -> 335 KB), translations -40% (it.js 143 -> 85 KB); routing,
day, panels, dashboard, map and boot time unchanged.
- i18n-check rejects labels the build cannot see (outside tr/trn/N_)
- tests/pages.test.js plays the shipped page in English, Italian and French
- docs/adr/0003, add-strings skill, ARCHITECTURE, README, CONTRIBUTING,
CLAUDE.md describe labels
tr('pnis.delivery_2_to_6_weeks') instead of tr('Delivery: 2 to 6 weeks'): the
English lives once, in src/i18n/en.js (inlined into the page at build, so no
extra request), and it/pt/fr map the same labels. Changing English wording no
longer renames a key in every dictionary.
- 2,899 labels, made from where each text is used and its first words; short
shared words are common.*
- plurals are one label with {one, other}: trn('label', n)
- static markup: data-i18n="label", data-i18n-aria-label, data-i18n-title
- saves from 1.33 and older stored English text in a few places; tr() still
resolves it
- i18n-check: undefined/unused labels, markup drift, plural shape; i18n-add.js
works on labels and --rename updates src/ too
- the old-branch port tool gives old English-keyed code and dictionaries the
same labels
Open (default, as before): route servers count, and incoming requests
are accepted on arrival. Selective: 70% of the requests, answered by
hand, and route server sessions stop counting, so you request peers at
each IX yourself. Closed: no requests, reputation sinks to -6, and
customer offers arrive 40% less often. The IX panel says when your route
server sessions are off because of the policy.
"Raise all max-prefix limits" answers every alert at once; leaks among
them become route leaks as usual, and the toast counts them.
- docs/adr/0001: GitHub Pages is the only host, not open for renegotiation
- docs/adr/0002: source in many files, shipped as one page assembled at build
- tests/pages.test.js: builds stay static files Pages can serve, all local
references resolve, only release.yml deploys and only via the Pages actions
- tests/build.test.js: partial naming and layout rules
- new skills: github-pages, edit-the-game; add-strings, performance, release
and write-tests updated for src/, sorted dictionaries and --base-ref
- CLAUDE.md, ARCHITECTURE.md, CONTRIBUTING.md (incl. porting older branches),
README.md and the PR template describe the new layout
- ACT is split by area into game/90-actions/*.js (const ACT in the first file,
Object.assign in the rest)
- CITY_LL, CITY_NUDGE and LANDS_LL have one entry per line; the id-keyed ones
are sorted
- site/i18n/*.js are sorted, one entry per line; i18n-check enforces it and
--fix (npm run i18n:fix) restores it; scripts/i18n-add.js adds, removes
and renames entries in place
- scripts/legacy/port-branch.js moves a branch's site/index.html edits into
src/ during a merge with main
- perf workflow and PR template build the base page with scripts/lib/page.js
A small city (P < 60) may not sit within 300 km of a bigger city in the
same country unless it is a cable landing or a capital (Canberra gets a
capital flag); a test enforces it everywhere. The 15 Brazilian cities
that broke it get off:true: still in the data so saves keep their POPs,
routing and links there, but new games do not draw them, offer them to
customers, list them in network presence, or let you build a POP there.
Brazil goes from 40 to 25 cities (Europe has 44). Order and Progress now
needs 15 IX.brrr ports.
site/index.html (900 KB of HTML, CSS and JS in one file) becomes src/: a shell
(src/index.html), styles/ and game/, concatenated in path order by
scripts/lib/page.js. The assembled page is byte-identical to the old file, so
load time and in-game performance are unchanged.
- scripts/build.js replaces build.sh (same env vars, same output)
- npm run dev: a zero-dependency dev server that assembles on every request
- tests assemble the page in memory; npm test runs every tests/*.test.js
- perf-bench takes --base-ref to build a git ref's page
- scripts/legacy/split-index-html.js is the splitter, kept for older branches
hwMul() scales new purchases of routers (routerCost, swapCost), optics
(optCost, on top of tariffs) and own builds (dfBuildCost, ownCabCost):
free for 180 days, then +4%/year, capped at +30%. Monthly costs of what
you own do not move.
Shortages are a new random event after day 180, never two at once:
optics +50%, routers +40% or builds +30%, for 45-75 days. Counter-moves:
stock spare optics from a dark fiber link at today's price, or buy a
365-day price lock from the NOC (80k + 30k per POP, double during a
shortage), which freezes today's trend and ignores shortages.
Measured on a 16-POP European network ($530k/mo revenue): the curve
adds ~5% of revenue a year in year 1 and ~23% by year 5 if every dollar
is reinvested in hardware; a lock costs about a month of revenue.
Big-network PNIs and augments now take 30 days, with a 15% chance of
6 to 12 months (still halved at a conference). Help and order text say
so.
Leased waves can be sold out on a route for a while: a stable verdict
per route, cable, size and 90-day window (2% for the smallest, rising
to 10% for the biggest), with a reason. The link window greys out sold
out sizes with the days left. Never in the first 90 days or the
tutorial.
IX.brrr Campinas, Equinox Ashburn IX and friends already say where they
are, so peering tips, IX LAG labels, the max-prefix leak incident, the
de-peering toast and the route server hint drop "in {city}" for them.
Christchurch (Garden-City-IX) and Invercargill on the South Island, which
had a coastline but no land to build on. Cook Strait Talking from Auckland
to Christchurch, and Lord of the Tasman Rings from Invercargill to Sydney,
Melbourne and Auckland, after the planned Tasman Ring Network that lands at
the Southland data centre campus. Kea, sandflies, post-hole diggers, ferry
anchors and the smelter's grid.
Saves with Australian POPs from before #148 get one notice: pricier transit,
fewer sellers, and Telstraya and Floptus sessions at the exchanges ended.
A POP name that would land on another name hides until you zoom in, unless
it is selected, hovered or home.
Every broker sale of 1-4 alien waves became its own customer, so a large
fiber-resale business grew to tens of thousands of tiny contracts. A real
save reached 124,966 alien-wave contracts and 49 MB: localStorage stopped
accepting it (save() swallows the quota error) and every compute() walked
the whole list.
A carrier that already rents waves on a fiber now grows its contract:
slots, monthly rate and the description add up. migrate() folds older
saves the same way, keeping the unhappier mood and the earliest start.
The same spectrum is sold and the same revenue is billed.
On that save: 124,966 -> 2,190 contracts, 49.3 MB -> 4.2 MB.
Each transit flow's backhaul round trip over your own links (2× the path
latency to the exit) now affects service: free up to 20 ms (~1,500 km),
up to 20% worse at 50 ms, and half the service value past 50 ms. sfOf()
multiplies delivery by it, so revenue, broadband growth and business
customers all feel it. Peering, PNIs and caches are exempt.
City panel chip and Transit-tab warning name the far exit and the round
trip; the NOC lists slow cities. Two tests updated: Moscow on Frankfurt
transit is still fully delivered but now slow, and the Red Sea test pins
Asian demand that would otherwise churn away on Marseille transit.
The NOC's 'Recent events' (S.log) becomes the notification inbox instead of
a separate one. Entries now keep a wall-clock time, a title, a repeat count
and what they are about, and the NOC shows the last ten minutes right after
the incidents rather than at the bottom: title, short text, 'n min ago',
x N for repeats within a minute, and Open.
Open targets come from the notice itself (incidents via their ref, DDoS,
badges, goals, exchange ports and sessions, resolved incidents), then from
its own navigation button, then from the city or link its text names; 45 of
46 notices in a 60-day test game get one. A link or customer that is gone
says so. Unread counts show on the NOC chip and the phone NOC tab (not red:
red stays for incidents). Entries are validated in sanitize().
Peering inbox (Networks tab): requests from small and made-up networks
arrive with every IX port, max-prefix alerts take bilateral sessions
down for a few weeks unless answered (raise the limit for growth, keep
it down for a leak; raising it on a full table is a route leak).
Unanswered mail costs reputation, which makes selective networks up to
10% pickier. The Large Peering Model agent costs $20M a year and gets
about a third of its decisions wrong, with a log to prove it.
PNIs are ordered, not instant: 2 to 6 weeks for small networks, 6 to 12
months for big content networks, Tier 1s and big eyeballs, for new PNIs
and augments alike (halved during a conference). Content networks and
Tier 1s start at 100G; Doitsche Telekomm sells 1G. Microsnoft refuses
PNIs and IX sessions in Ashburn, New York, Boston, Atlanta and Miami.
Only delivered PNIs carry traffic, bill, or count for goals and Tier 1.
After #133 the coastline router treated Egypt and Panama as solid land, so
Marseille–Singapore sailed round Africa (21,440 km instead of 12,175) and
Miami–Lima round Cape Horn (17,700 km for a 4,220 km hop). Real systems
cross both by land: Port Said to Suez beside the canal, and Panama
(PAN AM). These are now overland edges in the sea graph, priced as the
distance they cover. The Red Sea Crisis shuts Suez, and routes are cached
per set of open passages, also in the survey worker.
Long open-water legs follow the great circle where it stays at sea,
instead of a straight line on the map. The low-latency design may land
further off and backhaul overland, and may follow the corridor of the
fastest in-service cable on the pair when that is shorter, so it matches
Hibernia again (London–New York 25.3 ms, Halifax–London 20.9 ms) and
beats cables that take detours (Lagos–Bude 32.2 against 37.6 ms).
Tests: main's expectations restored where #133 had loosened them
(Marseille–Singapore needs no upgrades, New York–Sydney needs terminals,
express equals the fastest cable); the marine check knows the passages;
new checks for Suez, Panama, the crisis and the corridor rule.