--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/44/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/44/echoes" issue: 44 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Sevda Polat","Sable Whitford"] published: 2026-08-31 updated: 2026-08-28 articles: 15 --- # 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 44 — Echoes Past infrastructure decisions echoing in today's production realities ### Integration's Permanent Oscillation - [The Workaround Is the Pattern]() — By [Sevda Polat]() · Published 2026-08-28 · Format: Integration's Permanent Oscillation In 1984, IBM shipped a tool that let programs read a mainframe terminal screen character by character, pretending to be a human operator. It was fragile but immediately useful, because the cooperative alternative required both sides to agree, and agreement has costs that sort participants. Organizations that can afford structured integration get it; everyone else builds a workaround. Forty years later, AI agents are filling out web forms and clicking buttons for the same structural reason. The pattern predates the web. ### One Header's Long Deception - [The Header That Learned to Lie]() — By [Sable Whitford]() · Published 2026-08-28 In 1992, HTTP added a field called `User-Agent`. The [spec](https://www.rfc-editor.org/rfc/rfc1945.html) said it was for "statistical purposes" — a voluntary note from the client identifying itself. Unsigned, unverified, totally optional. ### The Integration Engineer - [Hank Delimitski Has Seen This Before]() — Published 2026-08-28 Somewhere between the first EDI transaction in the 1960s and the first AI agent filling out a supplier portal form last year, a generation of integration engineers built the bilateral plumbing of B2B commerce. They negotiated standards, wrote mappings, managed exception queues, and watched informal workarounds spring up around every formal connection they built. Most of them are retired now, or close to it. The knowledge they carry about what formal integration actually cost, why it broke, and what the workarounds were compensating for is fading just as a new wave of automation arrives to cross the same boundaries. ### Two Attempts at Resolution - [What RSS Couldn't Make Free Enough]() — By [Sevda Polat]() · Published 2026-08-28 · Format: Two Attempts at Resolution RSS asked almost nothing of publishers: a small XML file, no authentication, no negotiation. By 2008, half of consumer-media sites offered feeds. It was the lowest-cost path to universal machine-readable access anyone had tried. Then Twitter pulled its feeds, Google shut down Reader, and the platforms that controlled distribution stopped maintaining the side door. Even a cost that small was still a cost someone had to keep paying. - [What an API Costs to Keep Open]() — By [Sevda Polat]() · Published 2026-08-28 · Format: Two Attempts at Resolution If RSS was too simple to sustain universal coverage, APIs offered the opposite bet: structured, authenticated, richly documented interfaces between machines. By 2018, directories tracked over 19,000 of them. But each one is a commitment the provider has to keep renewing — versioned, supported, and eventually restricted when it costs more than it returns. Reddit's API still worked the day Apollo shut down. What changed was the price of using it. ### Further Reading - **Architectural Styles and the Design of Network-Based Software Architectures** — [Source]() — Published 2026-08-28 Fielding's 2000 dissertation designed REST for hypermedia, not APIs. Read what the industry skipped. - **Roy Fielding's Misappropriated REST Dissertation** — [Source]() — Published 2026-08-28 The industry borrowed Fielding's words and ignored his constraints. Good context for how API economics got weird. - **The Rise and Demise of RSS** — [Source]() — Published 2026-08-28 Netscape portal feature to format wars to platform defeat. The syndication arc rhymes with today's AI content fights. - **Key Web Scraping Court Cases** — [Source]() — Published 2026-08-28 Chronological legal tracker from eBay v. Bidder's Edge through hiQ v. LinkedIn to current AI scraping rulings. - **Requiem for Google Reader** — [Source]() — Published 2026-08-28 Reader's 2013 shutdown pushed content distribution toward closed feeds. The open web lost a quiet load-bearing wall. - **AI Crawler and Bot Traffic Statistics 2026** — [Source]() — Published 2026-08-28 Aggregates Cloudflare, Imperva, and Fastly data with methodology notes. Useful for comparing divergent traffic estimates. ### Past Articles - [Records Nobody Reads Until Something Breaks]() — By [Sable Whitford]() · Published 2026-08-20 · Format: Two Ledgers In 1983 a C program called syslog started appending timestamped lines to a file. It didn't check order, completeness, or who sent what, because the reader was assumed to be an engineer arriving after a crash. That append-everything, search-later model became the default shape of digital record-keeping. Agent audit trails are inheriting it now, and pointing it at a question it was never built for: not what broke, but what a system decided and whether it had the authority to decide it. - [The Ledger That Watches Itself]() — By [Sable Whitford]() · Published 2026-08-20 · Format: Two Ledgers Venetian merchants kept books that caught their own errors. A half-finished entry left a visible mark on the page long before anyone came to inspect it. Double-entry bookkeeping was a bet that the format should do the first pass of verification, so that discrepancies surfaced without anyone having to go looking. Most digital transaction systems dropped that bet and replaced it with access controls and audit policy. The difference matters when the trusted system is the one producing the errors. - [What the Log Couldn't Hide]() — By [Sevda Polat]() · Published 2026-08-20 · Format: The Logbook Thread When Judge Learned Hand found erased and overwritten entries in a ship's log in 1939, he did not simply discount the record. He treated the fabrication as evidence of concealment. That was the point of the book's physical design: a missing page number or a date out of sequence gave the tampering away. Digital event logs were built to answer a different question, and agent audit trails inherited that architecture. The question they will face in disputes and regulatory proceedings is the older one: can the surviving record distinguish an authorized action from an unauthorized one? - [AI Diffusion Through Two Channels]() — By [Sevda Polat]() · Published 2026-08-13 · Format: Machinery and Mirror Census data covering 117,000 firms shows 6.8% reporting that workers use AI for tasks while the firm itself doesn't register as an adopter. The spreadsheet precedent tells you what tends to happen when individual use outruns institutional oversight, and roughly how long governance takes to catch up. But agents call external tools and change records in systems their firm doesn't own, which is where the comparison stops being useful. ## Other sections in Issue 44 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()