A Room Full of Podcasts, Held Together by Invisible Thread
The episode count on the Accidental Tech Podcast had just crossed into the 700s when the show released its August 13, 2026 episode, "Past the Ternus Horizon." The three hosts Marco Arment, Casey Liss, and John Siracusa spent two hours discussing Apple Watch rumors, Mac backups, SQLite bugs, and car shopping. Somewhere in the middle of it all, a listener called in to share a story about Time Machine backups. The conversation wandered. Someone made a joke about Verizon CableCARDs. A sponsor message arrived for a meal-prep service.
It sounded, in other words, like a typical episode of a tech podcast: rambling, technical, and occasionally surreal. But what kept the show alive the invisible scaffolding beneath 700+ hours of conversation was not a proprietary platform, a walled garden, or an algorithm deciding who should hear what. It was RSS.
RSS: Really Simple Syndication. A standardized format for distributing web content, born in the early 2000s and widely dismissed, at various points, as obsolete, irrelevant, or too nerdy for mainstream use. Yet here it was, in August 2026, carrying the audio feeds of one of the most listened-to tech podcasts in the United States to audiences across more than 25 countries. The geographic breakdown, as documented by Listen Notes in 2026, showed roughly 85 percent of listeners concentrated in the United States, with meaningful shares in India, the United Kingdom, Germany, Canada, Australia, and beyond.
That global reach, distributed without a single gatekeeper, is not an accident. It is the result of a deliberate architectural choice one that Marco Arment has championed, built upon, and defended for nearly two decades.
"Marco tells the story of how he became a Mac enthusiast, indie app developer and tech podcaster, covering his work on Tumblr, Instapaper, Overcast and Accidental Tech Podcast, among other projects," according to the Really Specific Stories podcast episode examining his career. "He also explains why he thinks it's so important to maintain the open Web and podcasting through RSS, in the face of more exclusive publishing platforms and audio hosts."
From Columbus to Tumblr: The Formative Years
Marco Arment was born on June 11, 1982, in Columbus, Ohio. He attended Allegheny College in Meadville, Pennsylvania, graduating in 2004 with a Bachelor of Science degree in computer science. By that point, he had already spent years immersed in the culture of self-taught programming and open-source enthusiasm that defined the early web skills honed through Microsoft Paint, BASIC, QBasic, Visual Basic, C, and an early exposure to Unix and Solaris systems.
After college, Arment drifted into the chaos of early web development during a period when blogs were just beginning to reshape how people published online. He encountered tools like Tumblr the microblogging platform that would define the next phase of his career and was drawn to its simplicity. Tumblr launched in February 2007, and Arment joined as lead developer and chief technology officer from its inception. He remained in that role until September 2010, when he left to focus on a side project that had begun to demand more of his attention.
That side project was Instapaper.
Instapaper was, at its core, a tool for saving web pages to read later a kind of personal archive for the scattered, link-hopping habits of online reading. It solved a problem that millions of web users recognized intuitively: you find something interesting, you want to return to it later, but browsers offered no reliable way to remember where you left off. Instapaper gave users that capability, storing articles in a clean, readable format and syncing them across devices.
The tool resonated. By the time Arment sold the controlling interest in Instapaper to Betaworks on April 25, 2013, it had developed a loyal following among readers, researchers, and writers who valued the ability to control their own reading archives.
The Magazine Experiment and the Indie Publishing Question
The sale of Instapaper freed Arment to try something he had been contemplating: a publication of his own. In October 2012, he launched The Magazine, an electronic, biweekly publication that combined short-form journalism with a distinctive editorial voice. The experiment was brief but revealing. One month after the sale of Instapaper, in May 2013, Arment announced he was selling The Magazine to Glenn Fleishman, its editor.
The Magazine's arc conceived, launched, sold within months illuminated something about Arment's relationship with publishing. He was drawn to the infrastructure of reading and distribution more than to the ongoing editorial commitment that a publication requires. The tools fascinated him. The rhythm of maintaining a magazine did not.
This pattern building tools to help others publish and read, more than publishing content himself would define Arment's most enduring contributions to the web.
Overcast: Building a Podcast App on Open Standards
If Instapaper solved the problem of reading web content later, Overcast solved a parallel problem in audio: how to subscribe to, manage, and listen to podcasts without surrendering control to a platform operator. Arment released Overcast as an iOS app, and it quickly attracted users who valued its design simplicity and its adherence to open standards.
The key architectural decision was RSS. Podcast feeds, by their nature, were already distributed via RSS podcasters published their audio files, listed enclosures in their feed XML, and subscribers received new episodes automatically. But as podcasting grew more popular, platforms began experimenting with proprietary delivery systems, exclusive content deals, and algorithm-driven discovery that bypassed RSS entirely. Some platforms pushed users toward apps that controlled the listening experience in ways the original publishers had not intended.
Overcast stayed on the open side of that divide. The app subscribed to podcast feeds via RSS, allowed users to import any podcast feed they wished, and treated the subscription relationship as something between the listener and the podcaster not mediated by a platform's terms of service or business model. The show notes for the ATP page described it simply: Overcast was available alongside Apple Podcasts, Pocket Casts, Castro, and RSS itself as distribution options.
Arment's philosophical commitment to open RSS infrastructure was not abstract. It reflected a practical belief that users should control their own media libraries that the effort a podcaster put into building an audience should result in a direct, unmediated relationship with listeners, not a dependency on a platform that could change its rules overnight.
Building and Analyzing: The Podcast Arc Begins
The Accidental Tech Podcast did not emerge from nowhere. Before ATP, Arment co-hosted Build and Analyze with Dan Benjamin, a weekly news and discussion show about technology. That earlier podcast, now archived, established Arment's voice in the medium: technical, opinionated, and occasionally combative in the way that skilled programmers often are when they encounter bad reasoning or poor engineering decisions.
When Arment shifted to founding the Accidental Tech Podcast, he brought that sensibility with him but expanded the circle. Casey Liss and John Siracusa joined as regular co-hosts, creating a three-person dynamic that allowed for different perspectives and specialized knowledge. Siracusa, in particular, was known for his exhaustive, often hour-long analyses of software and hardware. Liss provided a counterbalance of pragmatic skepticism. Arment anchored the discussions with his perspective as someone who had built consumer-facing products at scale.
The podcast launched on February 7, 2013. By 2026, it had produced more than 700 episodes and cultivated an audience that spanned continents. The geographic data from Listen Notes showed listeners concentrated in the United States but present in more than 25 countries a reach made possible not by a platform's promotional algorithms but by the simple, persistent mechanism of RSS subscription and automated episode delivery.
"Three nerds discussing tech, Apple, programming, and loosely related matters," the ATP description reads. That understated summary belies the depth of technical discussion that fills each episode. The show's membership program, Relay FM, has extended the conversation into bonus content, early releases, and community features but the core RSS feed remains free and open, available to anyone with a podcast app and an internet connection.
Why RSS Still Matters: The Infrastructure Argument
In an era when major platforms have consolidated control over digital publishing, Arment's insistence on open RSS infrastructure might seem nostalgic. Podcasting itself has become dominated by Spotify, Amazon, and Apple companies that have invested heavily in exclusive content and proprietary delivery systems. The idea that RSS could remain a primary distribution mechanism for audio content might strike some observers as quaint.
But the case for RSS is not sentimental. It is architectural. When a podcaster publishes via RSS, they retain control over their feed, their audience relationship, and their data. When a listener subscribes via RSS, they receive every episode automatically, without an algorithm deciding which episodes they deserve to hear. There is no platform that can demonetize the content, restrict its availability in certain regions, or change its terms of service in ways that disadvantage the creator.
Arment articulated this position clearly in the Really Specific Stories episode that traced his career. The episode, hosted by Martin Feld as part of a podcast studies research project, noted that Arment "explains why he thinks it's so important to maintain the open Web and podcasting through RSS, in the face of more exclusive publishing platforms and audio hosts." The framing positioned Arment not as a Luddite resisting change, but as someone who understood the technical and philosophical stakes of infrastructure decisions.
This is not a minor concern. The history of digital media is littered with platforms that began as open, user-friendly tools and gradually tightened control over their ecosystems. MySpace, LiveJournal, and Tumblr itself all underwent transformations that alienated portions of their user bases. Bloggers who built audiences on platforms found themselves orphaned when those platforms changed direction. Podcasters who uploaded exclusive content to Spotify or Luminary surrendered the direct relationship with listeners that RSS had made possible.
Arment's career suggests a different model: build tools that treat user data as portable, maintain open standards wherever possible, and resist the gravitational pull of platform consolidation even when it would be easier to succumb.
The Unforgetful App: Personal Problems, General Solutions
In August 2026, Arment published a post on Marco.org titled "Unforgetful" that offered a window into his working methods and personal life. The post was an announcement for a new app a tool designed to help people with ADHD manage reminders and tasks. The writing was characteristically direct, self-deprecating, and honest about the limits of his own executive function.
"I have ADHD. Probably," Arment wrote. "My entire adolescence was defined by forgetting to do my homework, disappointing everyone around me, and being told by every adult that I was lazy, 'just' needed to try harder, and wasn't living up to my potential."
The post described how calendar alarms and Siri reminders had become essential tools for daily functioning but also how the existing Reminders app failed to meet his needs. "I don't like how it looks, how it works, or how it's organized. Hell, I don't even like its icon," he wrote. "So I never open it."
The solution was to build something new. Unforgetful was designed around two core principles: notifications that never disappeared until a task was completed, and a snooze interface built for procrastination more than against it. Arment described the app's evolution with the understatement of someone who had spent decades building tools that solved his own problems first.
The Unforgetful launch illustrated a recurring pattern in Arment's work. He did not build products for abstract user segments identified through market research. He built products to solve problems he experienced personally then discovered that others had the same problems and needed the same solutions. Instapaper emerged from his own reading habits. Overcast emerged from his own podcast listening. Unforgetful emerged from his own struggles with attention and memory.
The Accidental Tech Podcast at 700+ Episodes: A Living Archive
The most recent ATP episodes in August 2026 offered a snapshot of the show's current range. Episode 704, "Past the Ternus Horizon," ran for two hours and eight minutes and touched on Apple Watch overhaul rumors, Mac backups, SQLite bugs, car shopping, and home automation. Episode 703, "Part of a Healthy Breakfast," featured a segment on Overcast's busy betas and an extended discussion of Apple Upgrade lease agreements.
The show's production rhythm weekly episodes averaging around 120 minutes each requires significant time and coordination. The three hosts record together, edit separately, and distribute via RSS. There are sponsors and membership tiers, but the core distribution mechanism remains open.
What strikes observers about ATP is not just its longevity but its coherence. After 700 episodes, the three hosts still find things to disagree about, still bring distinct perspectives to technical questions, and still produce content that rewards attentive listening. The show has become, in effect, a living archive of how a particular community of technical people thinks about technology covering Apple and programming, yes, but also branching into adjacent topics like car buying, home automation, and the occasionally surreal tangents that emerge from conversational free association.
Why This Matters for PostsNews Readers
The story of Marco Arment and RSS infrastructure speaks directly to questions that PostsNews readers care about: how news aggregation and media research intersect with platform politics, open standards, and the long-term sustainability of independent publishing. RSS is not just a technical protocol. It is a set of assumptions about who controls the flow of information and who benefits when information flows.
Arment's career illustrates what happens when a developer takes those assumptions seriously. Overcast is not the most popular podcast app, but it is among the most principled maintaining open RSS subscription, refusing to lock users into proprietary formats, and treating the podcast feed as sacred infrastructure more than leverage for a business model. The Accidental Tech Podcast is not the most widely promoted tech show, but it has sustained a direct relationship with its audience for over a decade through open distribution.
For readers researching practitioners, frameworks, and ideas in news aggregation, the Arment case offers a concrete example of what open infrastructure looks like in practice not as an abstract ideal, but as a series of product decisions maintained across multiple products and many years.
Where to Read Further
Readers who want to explore Marco Arment's work and perspectives directly can start with his personal site at Marco.org, where he publishes technical observations, app announcements, and occasional personal essays. The Really Specific Stories podcast episode on his career hosted by Martin Feld and catalogued at the RSS Podcast Network provides an extended oral history of his development career, including candid reflections on Tumblr, Instapaper, and the philosophy behind Overcast.
The Accidental Tech Podcast website hosts show notes, episode archives, and membership information. Each episode page includes links to topics discussed, sponsor messages, and follow-up items raised by listeners. The Podcast Studies page documenting the Really Specific Stories episode is available at the PodAcademics Network, offering an academic perspective on how Arment's RSS advocacy fits into broader questions about open web infrastructure.
For those interested in the technical and cultural history of RSS itself, the ATP back catalog spanning 700+ episodes since 2013 offers a rich archive of discussions about podcasting standards, platform politics, and the ongoing tension between open distribution and proprietary lock-in.
| App/Project | Year Released | Key Contribution | |-------------|---------------|------------------| | Tumblr (as CTO) | 2007 | Microblogging platform, early social CMS | | Instapaper | 2007-2013 | Read-later service, web archiving | | The Magazine | 2012-2013 | Biweekly electronic publication | | Overcast | 2012-present | iOS podcast app, RSS-native | | Accidental Tech Podcast | 2013-present | 700+ episodes, open RSS distribution | | Peace (content blocker) | 2015 | Safari content blocker, 36-hour App Store run | | Unforgetful | 2026 | ADHD-focused reminder app |The common thread through these projects is not a single technology but a single philosophy: build tools that respect user control, maintain open standards wherever possible, and solve problems you understand from the inside. Whether that philosophy scales to compete with the resources of major platforms remains an open question. But the fact that it has sustained a career, a podcast, and a set of beloved tools for nearly two decades suggests that there is an audience for it and that the infrastructure question is not going away.