--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/21/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/21/echoes" issue: 21 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Nora Kaplan","Rina Takahashi"] published: 2026-03-22 updated: 2026-03-19 articles: 10 --- # TinyFish > CURRENT is a journal about AI agents in production, for the engineering and product leaders who have to make them work. Drawing on experience building enterprise web agents, it explains why the demo succeeded and the deployment didn't, and what that means for choosing vendors, briefing the board, and avoiding mistakes others have already made. [Read on the website]() ## Issue 21 — Echoes Past infrastructure decisions echoing in today's production realities ### The Standardized Bug - [The Specification of Being Wrong]() — By [Nora Kaplan]() · Published 2026-03-19 · Format: The Standardized Bug In 1996, the W3C published a specification telling browsers they were calculating the width of a box wrong. The browsers had shipped first. Millions of pages already depended on the "incorrect" math. Somebody had to give. ### The Typo That Shipped - [The Typo Every Browser Still Sends]() — Published 2026-03-19 In 1995, someone on an IETF mailing list pointed out that the HTTP "Referer" header was misspelled. Phillip Hallam-Baker, who'd proposed the field, cracked a joke about Daleks. Roy Fielding noted the Unix spell checker of the era wouldn't have caught either spelling. Everyone shrugged. ### Custodian of Errors - [The Woman Who Keeps the Web Wrong]() — Published 2026-03-19 Every major browser engine shipping today contains a rendering path whose explicit purpose is to be wrong. Wrong in the specific ways that Netscape Navigator 4 and Internet Explorer 5 were wrong, preserved with the fidelity of a museum restoration. ### Permanent Decisions - [The Fifty-Year Byte]() — By [Rina Takahashi]() · Published 2026-03-19 · Format: Permanent Decisions In the early 1970s, someone at Bell Labs made a quiet decision about how C would store text. No memo survives. That choice created the structural conditions for buffer overflow vulnerabilities, a category of harm that was understood by 1988, studied exhaustively through the 1990s, and the target of a billion-dollar defensive industry by the 2000s. None of it was enough. The flaw persisted for fifty years. Understanding arrived in the first twenty. - [The Clock Everyone Can See]() — By [Rina Takahashi]() · Published 2026-03-19 · Format: Permanent Decisions At 03:14:07 UTC on January 19, 2038, a counter running since 1970 will hit its maximum value and wrap to a date in December 1901. The math is simple. The fix exists. Everyone who needs to know, knows. Y2K mobilized hundreds of billions in global remediation through deadline pressure and concentrated blame. The 2038 problem has the same clarity and none of the same urgency. Twelve years out, the gap between knowing and doing has barely narrowed. ### Further Reading - **Back to the Building Blocks: The White House ONCD Technical Report on Memory-Safe Languages** — [Source]() — Published 2026-03-19 The federal government names C's memory model as a structural debt class spanning thirty-five years of vulnerabilities. - **DARPA's TRACTOR Program: Automated C-to-Rust Translation as a National Security Project** — [Source]() — Published 2026-03-19 When a language's legacy becomes a defense liability, DARPA funds machine translation at infrastructure scale. - **Memory-Safe Migration Will Take a Generation, Not a Policy Cycle** — [Source]() — Published 2026-03-19 Vaughan-Nichols frames the move away from C as a decades-long replacement problem with no clean cutover. - **The 2038 Problem Already Has a CVE, and Embedded Systems Aren't Patched** — [Source]() — Published 2026-03-19 Kaspersky identifies live vulnerabilities in fuel-gauge consoles as early evidence of 32-bit time overflow arriving. - **The 2038 Bug: Which Sectors Actually Face Risk from Legacy Time Representations** — [Source]() — Published 2026-03-19 Electropages surveys where 32-bit Unix timestamps still sit in production, with useful specificity about embedded systems. ## Other sections in Issue 21 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()