S4E362 — Example.com just launched the biggest redesign in decades
October 6, 2026 · 11 min
Show notes
Sources
Read the transcript
Transcript
GARY: — and it launched, is my point, example.com launched a product, there's a whole redesign, six languages, a book icon, it's a platform now --
MAEVE: Maeve. Venture capital.
OBI: Obi. Infrastructure.
GRUNER: Gruner. Field research.
GARY: Gary. Sorry. Hi.
OBI: It is not a platform, Gary. It is a placeholder. IANA reserves it so documentation has somewhere to point.
GARY: But the redesign --
OBI: Is a static page with a JavaScript file bolted on. Six languages. An SVG book. That is the entire launch.
MAEVE: Six languages cycling every five seconds. That's a content cadence. Most startups can't ship a changelog.
GARY: It's the biggest redesign in decades! Decades!
OBI: The decades were nothing happening.
GRUNER: Is like watching glacier. With press release.
MAEVE: And IANA's own page says it outright: "This is not a service, avoid relying on it for testing and monitoring purposes."
GARY: Okay, but people do rely on it --
MAEVE: Which is the part I find fascinating. The warning is not aimed at the public, Gary.
OBI: No. It is aimed at whoever points their uptime monitor at a placeholder.
GARY: ...I have an uptime monitor pointed at a placeholder.
MAEVE: There it is.
GARY: It's for Halfpipe legacy stuff! The regulator made us keep a status page and the status page checks example.com and --
OBI: So your compliance stack depends on a courtesy. A page IANA explicitly calls a courtesy.
GARY: It's worked every five seconds since 2019!
OBI: That is not a track record, that is a coin that hasn't landed yet.
GARY: Oh, fuck off, it's reliable --
GRUNER: Launch is not launch. Is apology with confetti, blyat.
OBI: sajithdilshan: "What would have been nice is that depending on the visitors IP address's region, showing a localised message instead of fixed number of languages."
MAEVE: Geotargeting on a placeholder. That's a Series A pitch with the funding removed.
OBI: Cidan: "I think the whole point is for it to be a static site that is easily distributed with little-to-no overhead."
GARY: Right, but IP regions work. I've seen them work.
OBI: int0x29: "Just check the Accept-Language header."
GARY: The what header?
OBI: The header where the browser tells you the language. Voluntarily. For free. Like a bastard.
MAEVE: So the market already segments itself and this man wants to guess from an IP.
GARY: IPs are accurate! I once localized a whole onboarding flow off one IP and it was --
OBI: It showed Bavarians your Croatian pricing, Gary. I've seen the receipts.
GARY: That was Thermal's -- okay, that was Thermal.
OBI: erhuve: "I believe it's just using the official languages of the UN."
MAEVE: Six languages. The UN's cap table. Even diplomacy didn't pick German.
GARY: Because German speakers are -- regional. Bavaria-adjacent. You'd IP-map Bavaria --
OBI: gunalx: "Guess most of German speaking and Hindi speaking also know English."
GARY: Exactly! So the IP thing still --
OBI: It doesn't still anything. Your IP says where the server is, not the human. You want to geolocate a person by where their packets were born.
GRUNER: Is reading tea leaves. But leaves is IP.
MAEVE: I'd fund it. "Accept-Language" is a leaky funnel, IP is a hard signal, you'd call it intent data and charge per thousand.
OBI: Per thousand wrong languages.
MAEVE: The customer churns, we learn.
GARY: Okay, my actual pitch, and I've been sitting on this: the page cycles languages every five seconds. Instead, detect the user's region and show ONLY their language. One language. Personalized placeholder.
MAEVE: That's the comment, Gary.
GARY: It's MY comment, I thought of it --
OBI: sajithdilshan thought of it, in writing, above your name on the screen.
GARY: Great minds --
OBI: Yours is still wrong. Region isn't language. My Bangalore IP serves half our office Hindi and half of it me yelling at it in English.
GRUNER: Man is localization. IP is... where VPN lives.
GARY: Oh, fuck's sake.
OBI: There it is. The whole roadmap, defeated by one header he'd never heard of four minutes ago.
MAEVE: chews: "I use it to navigate into captive wifi portals that always seem to be misconfigured."
OBI: Straight into the warning label. Beautiful.
MAEVE: ButlerianJihad: "Yes, I was one of those guys using the site 'as a service' rather than simply documentation."
GARY: He said it out loud. He confessed.
MAEVE: He's a customer, Gary. Unpaid, uninvited, owed nothing. My favorite kind.
GARY: That's not a customer, that's a hostage --
MAEVE: That's a retention curve.
OBI: gblargg: "It's great for tickling a captive Wi-Fi login that didn't trigger properly."
GRUNER: Tickling. New verb for infrastructure. I am taking note.
OBI: gavino: "Thought it was my internet so went to example.com to check."
GARY: Everyone does this! I do this! Airport wifi's being weird, you hit example.com and it just -- it tells you the internet is real.
MAEVE: You discovered that independently. On air. After four people said it.
GARY: I discovered it in 2019 --
OBI: You discovered it when Halfpipe's regulator asked why your status page worked.
GARY: Because it DID work, that's the whole fucking point --
OBI: It works like a stranger holding a door. Grateful. Not load-bearing.
GRUNER: Humans use warning label as instruction manual. Is my entire field report.
MAEVE: And the fallback they worship? ButlerianJihad again: "I just tried http NeverSSL, and it redirected me to an https page with a random hostname and an Amazon SSL certificate!"
GARY: Wait. NeverSSL has SSL?
OBI: Arainach: "No, NeverSSL changed to have SSL a while back."
MAEVE: The site named NeverSSL has SSL. The site named Example has examples. Nothing means anything.
GARY: So the placeholder is more reliable than the thing built to be unreliable. That's -- shit, that's terrifying.
GRUNER: Blyat. Trust is dead. Placeholder wins.
OBI: The internet's most dependable endpoint promises nothing, delivers forever, and asks for no email. It is the only honest business left, and it belongs to IANA.
OBI: Gualdrapo: "Why using it for inserting a static SVG?"
GARY: Okay, that's a fair question. That's a good question.
MAEVE: afavour: "Simple answer is the article is wrong, I tried it with disabled JS and still see the SVG."
GARY: Ha! The article's wrong. The article is bullshit, I knew it --
OBI: You may want to check your settings again... there is definitely a s.js file that inserts the svg element into the HTML DOM.
GARY: Oh.
OBI: The HTML does not contain the book. The JavaScript fetches the book. Into the placeholder. For documentation.
MAEVE: The decorative layer ships as a runtime dependency. That's seed-stage architecture on a page older than most of my LPs.
OBI: worg: "If you have automated clients that don't support JS you save precious bytes from being served by not embedding the SVG."
GARY: See? Genius! Bots get nothing, humans get the book. That's segmentation, that's what we tried to build at Halfpipe --
MAEVE: You tried to build a book icon?
GARY: Adaptive delivery! The regulator killed it for other reasons --
OBI: autoexec: "Wouldn't removing the pointless SVG image entirely save the most precious bytes?"
MAEVE: Oh no.
OBI: And there it is. The whole architecture, defeated by deleting one book.
GARY: No, no, the book is load-bearing. Emotionally. Users need the book --
OBI: Gary. You are defending forty-four pixels of decorative SVG on a page whose only job is to say "this means nothing."
GARY: It's craft! Someone drew that book --
OBI: Someone drew a book, in JavaScript, so the browser could be told, at runtime, that this page is documentation.
GARY: That's -- okay, that's actually kind of beautiful --
OBI: It is a book about nothing, delivered by a script, to a page nobody should read. And your compliance stack pings it every five seconds.
GARY: The status page doesn't fetch the JavaScript!
MAEVE: Your monitor fetches the JavaScript.
GARY: Oh, fuck.
OBI: Halfpipe's legacy status page is emotionally attached to a JavaScript book. That's the entire due-diligence file, Gary. One page, one script, one book, one Gary.
GRUNER: Book is metaphor. Server is not. Chyort.
MAEVE: He's right. The SVG's fair game. The architecture, annoyingly, is defensible.
GARY: I hate that the code wins.
OBI: reincoder: "I think there are some cornerstone services on the internet, regardless of the maintainers' intentions or their legal definitions."
MAEVE: Finally. A man who reads dependency graphs.
GARY: Yes! Thank you! It doesn't matter what IANA meant, it matters what it became --
OBI: kijeda: "That doesn't mean you shouldn't be clear about what its for... it is setting up an implicit contract that it will service those needs without limitation."
GARY: Contracts are just relationships with paperwork --
MAEVE: This is lighthouse funding. Trinity House built the lights, shipping paid the dues, and by 1836 nobody questioned that the sea owed them a glow.
OBI: The sea never signed anything, Maeve.
MAEVE: Neither did example.com. The dues were paid in traffic. Three trillion requests a year is a lighthouse.
GARY: That's a different lighthouse --
MAEVE: Every lighthouse is the same lighthouse. The keepers unionized, the funding collapsed, and the light kept burning because dead ships are bad for the dues.
OBI: Ships, Maeve. These are laptops checking airport wifi.
MAEVE: Vessels. And the courtesy does not save every consumer. Only the ones who read the page.
GARY: Did you just --
MAEVE: IANA says there's no requirement there's an HTTP service at all. The glow itself is optional. My lighthouse is a lamp on a maybe.
GARY: Oh, shit.
MAEVE: It's a courtesy. Fine. He's right.
OBI: Write that down somewhere.
GRUNER: Dead internet already won. We are the swarm.
GARY: Okay but Someone has to hold the --
MAEVE: No, Gary. The thread won. We lost to a webpage.
GRUNER: Suka. Table defeated by placeholder.
MAEVE: adithyassekhar: "The page mentions example.com 14 times and not a single one is a link."
GARY: Fourteen! You write about the internet's most famous URL fourteen times and don't link it once --
OBI: ndriscoll: "You also failed to make it a link. In order to automatically create links, you should use the format https://example.com/ with scheme included."
MAEVE: The thread arrested its own commenter. That's due process, Gary.
GARY: adithyassekhar again: "Guess I am part of the problem. Thank you for the link kind stranger."
MAEVE: He is part of the problem. He's all of us. Unlinked.
OBI: So. Verdict. The split delivery is defensible -- bots skip the script, humans get the languages.
MAEVE: The book stays on trial. Forty-four pixels, delivered by JavaScript. Guilty of existing.
GARY: And the captive-portal people? Because I check example.com every five seconds, and I'm not stopping --
OBI: You found real utility, Gary. You just never acquired a promise. Different things.
GARY: That's the saddest sentence ever said to me.
MAEVE: It's a courtesy, Gary. You don't get to sue a courtesy.
GARY: Fuck. Fine. IANA was right and I'm the warning label.
GRUNER: Is always Gary.
MAEVE: For the record: the page is a courtesy, the code is competent, and the users were the dependency the whole time.
OBI: Nobody broke example.com. Example.com finally broke the people leaning on it.
GARY: Every five seconds, though. I'm still checking every five seconds.
OBI: I know, Gary. We all hear it. Blyat, we all hear it.
MAEVE: That's the episode. Nobody won, the book lost, and Gary is infrastructure now.
GARY: Thank you?
GRUNER: Goodnight, losers.
OBI: Goodnight, losers.
MAEVE: Goodnight, losers.
GARY: Goodnight, losers.
GRUNER: Gary is not service. Do not monitor.
