The left panel's four tabs overflowed its 272px width on tablets and small
laptops: Goals wrapped its count, Networks ran off the edge. Counts now sit
on the tab's corner, labels stay on one line and shrink last.
Backbone, Auto-TE and DDoS settings sat below every notification in the NOC
tab. A Routing & DDoS button at the top opens them in a modal that redraws
in place after each action, with a red dot when Auto-TE is paused.
Every flood was 700G or more from day 1, so the scenario no longer built up. Sizes
are 1.36's again (a third terabit monsters, the rest ordinary floods sized to the
city), growing by the year as #153 had it. Floods go for POPs that serve someone,
and a city with nobody to serve only holds a flood its tools soak up. Seeded runs
over a year: no defence or one 1T center cannot win; one 1T center with full
Flowspec and clean pipe wins around day 100 (main needed two centers, day 164).
Frederic's call for 2.0: keep #153's fixes, NOC breakdown, new vectors, gaming risk
and overlapping attacks, but not the per-port model. It split every flood over each
ingress port with traffic (over a thousand on a big network), stored them all in the
save, routed one pinned flow per port, and with it came the build-order and
victim-scoring bugs found in review.
Each attack is again one entry port at the victim (a.entry): upstream clean-pipe,
Flowspec on the victim's router, IX blackholing, a sacrificial PNI and RouteScript
filter it in that order (ddosMitigation), then scrubbing; what leaks is junk at the
victim spread like its traffic, exactly as on main. Saves from 2.0 builds with
a.entries load: sanitize drops the shares and a 'distributed' entry becomes 'edge'.
Removed: R.ingressPorts, ddosEntries/ddosFold/ddosSlices/ddosCities/ddosHasIx, pinned
flows (and the pinned-rank handling in routing and its reference), the mixed-TCAM
line and the 'across N ports' message, and their tests; the scrubbing source-city
test now uses two victims sharing one center. CHANGELOG #153 bullets describe what
ships and credit #153.
Scale normal attacks with network demand, level and gaming exposure, with
randomized sizes, durations, overlapping attacks and distributed ingress.
Set average sizes to three times the non-gaming baseline at one gaming
customer and eight times at fifty. Keep Flood Season escalating after its
challenge ends.
Add gaming-specific vectors, Memcached amplification and ACK floods.
Account for upstream scrubbing, Flowspec and shared scrubbing capacity in
sequence. Show precise mitigation totals and one destination-based
scrubbing detour in existing live attack cards.
Keep each source-to-scrubbing route distinct in link traffic breakdowns,
including the source label, Open button and map highlight.
Include deterministic tests, old-save migration and translations.
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().
A link's routing metric could only be one of four presets (Prefer,
Normal, Avoid, Backup only). Links now also get a Custom option, closer
to how real networks tune IGP metrics:
- Multiplier mode scales the distance cost, (km + 60) × 0.1 to 100.
- Cost mode sets an exact cost, 1 to 65535 like an OSPF metric.
The preset buttons stay plain. Picking Custom explains how a link's cost
is worked out and lists what each preset comes to on that link. Choosing
Custom starts from the current preset and switching modes keeps the
effective cost, so nothing moves until the player changes the value.
Like the presets, it applies to every link between the two cities.
The cost formula lives in one helper, linkW(), used by compute() and the
traceroute paths. Custom links store mk/mv, which sanitize() repairs and
clamps; old saves load unchanged. The link panel skips its daily
re-render while the number field has focus, and Enter applies the value.
Tests cover routing equivalence with the presets, rerouting by cost,
mode switching, input clamping, saves, and the panel at desktop and
phone width. French, Italian and Portuguese for the new strings.
Perf on the big network: no change beyond noise, routing identical to
main.
S.scrubAt/S.scrubTier become S.scrubs, one center per city, each with its
own size and monthly fee; old saves carry theirs over in sanitize().
An attack goes to the nearest working center with a backbone path, and
spills to the next when it is full. A remote center's flood (plus a share
of the victim's own traffic) is reserved along the backbone path after
the L2 circuits, like a circuit: it fills those links, the round trip is
shown in the NOC, and what the links cannot carry is not scrubbed and
lands on the city. Local centers behave as before.
DDoS protection customers lose mood while their attack detours 30+ ms,
with the reason in their row; a new requirement asks for a center on the
customer's continent. The Infra tab names the nearest center and its
distance, and How to play explains it.
A goal to build your first scrubbing center, and badges for weathering an
attack, holding a multi-terabit flood, running a clean-pipe or a sacrificial
PNI, blackholing your own city, and landing a HackBack that works. New stats
track the hold/monster/hack-win counts; Italian and a test included.
Rounds out the DDoS toolbox. Scrubbing centers come in 100G/1T/10T tiers and
clean only up to their capacity; always-on or cheaper on-demand (which lags a
couple of days). A transit clean-pipe add-on scrubs a flood upstream before it
reaches you. A Chinese PNI can be marked sacrificial: a flood over it dies on
the small port instead of the core, at the cost of half its legit capacity. A
new IX-blackhole mitigation drops about half the junk while keeping the victim
up. Selling DDoS protection now carries an SLA penalty when a protected
customer still goes down. Italian and tests included.
Flowspec was a flat network-wide licence. In reality the drop rules live in
hardware TCAM, and the budget differs by platform, so flowspec is now a
router-model capability: none on the used Rusty, a little on merchant-silicon
and whitebox models, full on the big chassis. The flood is filtered only where
the attacked POP's router can do it, and a bigger TCAM knocks it down further.
The licence is gone; the NOC shows how many POPs are capable and the attack
panel names the chassis doing the filtering.
DDoS was one flat random event. Now each attack has a vector (DNS, NTP,
CLDAP, SYN, HTTP), a size from a few Gbps to a multi-terabit monster, a
target POP, a duration and an entry point among that city's uplinks.
The NOC grows a live attack panel and a toolbox: RTBH (free, instant, but
the victim goes dark too), a one-time Flowspec licence that drops known UDP
floods at the edge but cannot touch an HTTP flood, the existing scrubbing
center, and HackBack 3000, which sometimes ends the attack and often
flattens an innocent for a fine. New Vigilante and Collateral Damage badges,
Italian translations, and tests for the attack, each tool and old saves.
New POPs in Milan, Rome, Palermo, Lisbon, Athens, Atlanta, Denver, Phoenix,
Boston, Houston and Salt Lake City, with cables and local networks.
Big metros get challenger exchanges with overlapping but different members.
IX state is now keyed by exchange id instead of city. Sixty small networks
sit on random exchanges. EU ports are cheaper and see price wars, and
Voda-Phony moves to paid peering only.
Tap the cash chip to open the bank. Lenders make loan offers now and
then, and much more often while you are in the red, so a bad hour no
longer has to end in bankruptcy.
- Eleven lenders with their own rates, terms and odd conditions, from
Goldman Sacks (A rating and up) to the Loan Shark (always open, sends
"reminders" when you are late).
- Conditions are checked daily: 15 days of grace, a warning, then a
penalty added to the balance every 30 days while broken.
- Credit rating from revenue, profit, cash and payment burden decides
which banks will talk to you.
- Crypto Bros pay out in a volatile TubeCoin; Venture Vultures take a
share of revenue instead of repayments and can be bought out.
- Repay early for a 2% fee. Payments show up in costs and the NOC
dashboard.
Closes#1Closes#2
Stuttgart has no transit for sale and no private interconnects: the
Spätzle-IX is the only way to exchange traffic locally, otherwise haul
it to Frankfurt. Frankfurt and Stuttgart get small display-only nudges
so they don't overlap on the map; distances still use real coordinates.
Bundle up to 8 identical ports to the same transit provider, IX or PNI.
Each member costs a full port and adds capacity; flow hashing is never
perfectly even, so a bundle carries about 95% of the sum. Upgrading the
port speed upgrades every member.
Also fix goals completed on day 0 paying their reward again on every
action that day.
A cartoon browser game about building the internet, deployed to
https://seriesoftub.es from published releases only.
- site/: the single-file game plus favicons, app icons, manifest,
social image, robots.txt, sitemap.xml, llms.txt and a 404 page.
- Full SEO head: canonical URL, Open Graph and Twitter cards,
WebSite and VideoGame structured data, noscript fallback.
- Cookieless Ridiculytics analytics via stats.seriesoftub.es, pinned
with SRI and active only on the production domain.
- Headless test suite (node:test + jsdom), CI on every push, and a
release workflow that verifies the tag, tests, builds, deploys to
GitHub Pages and pings IndexNow.