Some technologies die because they were inferior. Some die because they were replaced by something genuinely better. And some die not because they failed, but because they succeeded too well at something that powerful companies needed to stop. RSS belongs in the third category. It was not beaten in the marketplace by a superior alternative. It was starved to death by companies whose business models could not tolerate the kind of open, user-controlled information flow that RSS enabled.

To understand why this matters, you first need to understand what RSS actually is. RSS stands for Really Simple Syndication, and the name is honest. It is a plain XML file that sits on a web server and lists the most recent content from that site — blog posts, news articles, podcast episodes — with a title, a link, a publication date, and either a summary or the full content. A piece of software called an RSS reader checks that file periodically, usually every hour or every few hours, and shows you new items when they appear. That is the entire protocol. There is no authentication layer, no analytics pipeline, no recommendation algorithm, no advertising slot, no user profile. The server publishes a file. The client reads it. Nothing in between.

This simplicity is not a limitation. It is the feature. RSS is a pull protocol. You, the user, choose which feeds to subscribe to. Your reader fetches them directly from the publishers’ servers. No third party mediates the exchange. No intermediary decides what you should see. No company collects data about what you read, when you read it, or what you click on afterwards. You are not a user to be analysed and monetised. You are just someone reading things on the internet, the way the internet was meant to work.

In the early 2000s, this model thrived. Every blog had an RSS feed. Every news site had one. Every forum, every wiki, every content management system generated RSS automatically. Podcasts adopted it as their distribution backbone and still use it today — every podcast you have ever listened to was delivered to your phone through an RSS feed. The protocol was so ubiquitous that it became invisible, like HTTP or DNS. You did not think about using RSS any more than you thought about using TCP. It was just how content moved from publishers to readers.

Then Google decided to get involved. In 2005, Google launched Google Reader, a web-based RSS aggregator that pulled feeds into a clean, fast interface with keyboard shortcuts and a simple reading experience. It was excellent. By most accounts, it was the best RSS reader ever made. At its peak, Google Reader had over thirty million users, making it the dominant interface for consuming RSS feeds. For millions of people, Google Reader was RSS. It centralised the experience while preserving the underlying decentralised protocol, much like Gmail did for email. Publishers could still publish independent feeds. Users could still subscribe to whatever they wanted. Google Reader provided the convenience layer on top without breaking the openness underneath.

If the story had ended there, RSS might still be the dominant content distribution mechanism on the web. But Google also acquired FeedBurner in 2007, a service that added analytics and advertising to RSS feeds. Publishers with FeedBurner-wrapped feeds could see subscriber counts, click-through rates, and engagement metrics. They could also insert Google ads into their feeds. This seemed like a natural evolution — make RSS sustainable for publishers by giving them monetisation and measurement. But it also inserted Google into the middle of what had been a direct publisher-to-reader relationship. The feed was no longer just a file on the publisher’s server. It was a file served through Google’s infrastructure, with Google’s tracking code, delivering Google’s ads. The intermediary had arrived.

Then, on 13 March 2013, Google announced that it would shut down Google Reader. The stated reason was declining usage. In a blog post that has since been widely mocked for its tone-deafness, Google claimed that Reader’s users could export their data and find alternative services, as if the problem was a simple matter of switching apps. The internet erupted. Thirty million people do not constitute a declining user base for most products. For Google, which measured success in billions, thirty million was a rounding error. But the anger was not just about losing a convenient tool. It was about losing the centre of gravity that kept the RSS ecosystem coherent. Google Reader was the default. When it disappeared, millions of users who had never thought about which RSS reader to use were suddenly forced to find one. Most of them did not. They stopped using RSS entirely, and the ecosystem never recovered.

The conventional narrative about Google Reader’s death is that Google killed it because it was not making enough money, or because Google wanted to push users toward Google Plus and Google News, or because Larry Page’s infamous spring cleaning rationalised the product portfolio. All of these explanations contain some truth, but they miss the structural reason. The real reason is that RSS as a protocol is incompatible with the surveillance advertising business model, and Google is fundamentally a surveillance advertising company. It is not a technology company. It is not a search company. It is an advertising company that uses technology to gather data about people so it can sell their attention to advertisers. RSS, by its nature, makes that impossible.

Consider what happens when you read a news article through an RSS reader. Your reader downloads the article directly from the publisher’s server. Google is not involved. It cannot see what you read. It cannot track how long you spent on the article. It cannot serve you a targeted advertisement based on the article’s content or your reading history. It cannot build a profile of your interests over time. It cannot link your reading habits to your search history, your YouTube views, your location data, or any of the other signals it uses to build the advertising profile that generates nearly all of its revenue. You are invisible to Google while using RSS, and invisible users are worthless to an advertising business.

Now consider what happens when you read that same article through Google News, or through Chrome’s discover feed, or through any of Google’s content surfaces. Google knows exactly what you read. It knows what you read before this article and what you read after. It knows whether you scrolled to the end or bounced after the first paragraph. It knows whether you clicked on an advertisement alongside the article. It can correlate all of this with your search history, your location, your demographic profile, and the thousands of other data points it has collected about you. This is not a side effect of how Google delivers content. It is the entire point. The content is the bait. The data is the catch.

From a business perspective, an RSS user is a lost opportunity. Every minute you spend reading content through an RSS reader is a minute you are not spending on Google’s properties, generating data that Google can monetise. Every article you discover through an RSS feed is an article you did not discover through Google Search, where you would have seen advertisements and contributed data to Google’s ranking algorithms. The protocol disintermediates Google entirely. It removes the middleman between the reader and the writer. For a company whose entire business depends on being the middleman, this is an existential threat.

The threat goes deeper than just lost advertising inventory. RSS threatens Google’s role as the gatekeeper of information. When you use RSS, you decide what sources are worth your attention. You curate your own information diet. You are not dependent on Google’s algorithms to surface content, and Google cannot manipulate what you see to optimise for engagement or advertising revenue. The algorithmic feed, which powers everything from Google News to YouTube to the Chrome new tab page, is fundamentally about taking control away from the user and giving it to the platform. The platform decides what you see. The platform decides in what order. The platform decides which content to suppress and which to amplify, based on whatever mixture of engagement metrics, advertiser preferences, and internal business goals it has chosen to optimise for. RSS does the opposite. It gives the user complete control over which sources to follow and presents everything in simple chronological order, with no algorithmic curation whatsoever. Every minute you spend in an RSS reader is a minute spent outside the algorithmic attention economy.

This is not speculation about hidden motives. Google’s internal incentives make the conclusion inevitable. Google is a publicly traded company with a fiduciary duty to maximise shareholder value, and its shareholder value depends almost entirely on advertising revenue. In 2012, the year before Google Reader was shut down, Google earned over forty-three billion dollars in advertising revenue, which was over ninety-five percent of its total revenue. Every product decision at Google is made in the context of that dependence. A product that serves tens of millions of users while generating no advertising revenue and actively reducing the amount of time those users spend on Google’s revenue-generating properties is not a product that will survive an honest internal cost-benefit analysis. The surprising thing is not that Google Reader was killed. The surprising thing is that it lasted eight years.

What happened after Google Reader’s shutdown confirms the structural diagnosis. In the years that followed, Google invested heavily in products that solve content discovery in ways that are fully surveillance-compatible. Google News became more personalised and more integrated with Google’s advertising infrastructure. The Chrome new tab page evolved into a content recommendation feed driven by Google’s behavioural data. Google Discover, launched in 2018, is essentially an algorithmic feed that shows you content Google thinks you will find interesting, based on everything it knows about you. These products all serve the same basic need that RSS served — keeping you informed about content you care about — but they do it in a way that keeps Google in the middle, collecting data and serving advertisements at every step. They are RSS rewritten for the surveillance age.

Google was not alone in this shift. Facebook’s News Feed, launched in 2006 and refined continuously since, is an algorithmic content feed designed to maximise time on site and advertising impressions. Twitter’s timeline moved from chronological to algorithmic by default, then offered users the option to switch back, then made the algorithmic feed increasingly difficult to escape. Even Apple, whose business model is less dependent on advertising, introduced Apple News with a heavily curated, algorithmically driven interface rather than embracing RSS as the open standard it had always been. Across the industry, the pull model of RSS was replaced by the push model of algorithmic feeds. The user’s choice of what to read was replaced by the platform’s calculation of what would maximise engagement. The transaction was made invisible, but the cost was the same as always: your attention, your data, and your autonomy.

The death of RSS also accelerated the centralisation of web publishing. When RSS was ubiquitous, a small independent blog with a thousand readers could reach those readers directly through their RSS clients. The blog did not need to appear in Google Search, did not need a Facebook page, did not need to optimise for any algorithm. It just needed to publish an RSS feed, and readers who had subscribed would receive every post. This was a genuinely decentralised content distribution network in which reach was determined by reader choice rather than platform amplification.

Without RSS as a reliable distribution channel, independent publishers became increasingly dependent on the platforms. If Google decided not to index a site, it disappeared from search results. If Facebook decided not to show a post in the News Feed, it disappeared from social media. The switch from pull to push was also a switch from independence to dependence. The platforms did not just capture the readers. They captured the publishers too, because the publishers had no other way to reach their audience. The market appears diverse at the surface — there are millions of websites, thousands of news outlets, countless blogs — but the distribution pipes that connect them to readers are controlled by a tiny number of companies. RSS was an alternative pipe. Killing it meant killing the competition to the pipe.

The effects on the quality of information are harder to measure but impossible to ignore. An algorithmic feed that optimises for engagement will, by its nature, promote content that generates strong emotional reactions. Outrage spreads faster than nuance. Simplistic takes spread faster than careful analysis. Headlines written to provoke clicks spread faster than headlines written to inform. The RSS model, with its chronological timeline and user-curated source list, is immune to these dynamics. You see what the sources you chose have published, in the order they published it. There is nothing to game. No algorithm to manipulate. No viral dynamics to exploit. The reader’s attention is directed by their own judgment rather than by an engagement-optimising machine learning model. When RSS died, so did the most effective defence against algorithmic information distortion.

Podcasts are the exception that proves the rule. Podcasts never abandoned RSS, and they remain the one major content format where the open protocol has survived intact. Every podcast app, from Apple Podcasts to Spotify to Pocket Casts, is fundamentally an RSS reader with an audio player attached. The podcast creator publishes an RSS feed containing audio file links and metadata. The app fetches that feed and presents new episodes to the user. It is the exact same architecture as text-based RSS, applied to audio. And podcasting is thriving. It is a multi-billion-dollar industry with hundreds of millions of listeners, vibrant independent creator ecosystems, and a distribution model that still operates largely outside the algorithmic walled gardens. The technology works. The business model works. The only reason text-based RSS did not follow the same trajectory is that the companies controlling text-based content distribution — Google, Facebook, Twitter — had the power and the incentive to kill it. Podcasting survived because Apple’s dominance in the early podcast player market meant that no single advertising-driven company had the leverage to force a transition to a proprietary alternative. The protocol survived because the control was fragmented.

There are signs that RSS is making a quiet comeback, driven by the same forces that have made self-hosting, encrypted messaging, and decentralised social media attractive to a growing number of people. The newsletter boom, led by Substack, Ghost, and Buttondown, is essentially RSS delivered through email. The writer publishes a post. It goes out to subscribers. They read it in their inbox, in chronological order, without an algorithm mediating the experience. The delivery mechanism is email rather than RSS, because email is the one pull-based protocol that never lost its user base, but the model is identical. Many of these newsletter platforms also publish RSS feeds alongside their email deliveries, and dedicated RSS readers are seeing renewed interest. Feedbin, Feedly, Inoreader, and NetNewsWire are active, well-maintained projects with growing user bases. The open-source reader Miniflux has a dedicated community and a clean, fast interface. FreshRSS lets you host your own reader on your own server, which is the ultimate form of RSS sovereignty.

The Fediverse, the network of interconnected servers running ActivityPub-based software like Mastodon, Lemmy, and Pixelfed, is another RSS revival in all but name. When you follow someone on Mastodon, you are subscribing to their ActivityPub feed, which is an RSS-like stream of their posts delivered directly from their server to yours. The protocol is different from RSS in its technical details — it uses JSON rather than XML and supports bidirectional communication rather than just publication — but the architecture is the same. You choose who to follow. Their content comes to you. No algorithm decides what you see. No advertising platform monetises your attention. It is RSS’s philosophy applied to social networking.

The broader lesson is that open protocols do not fail because they are technically inferior. They fail when companies that profit from intermediation have the power to strangle them. RSS was a threat to Google’s business model not because it was better at delivering content — though it was — but because it was better at excluding Google from the transaction. Every open protocol that gives users direct access to content or services without a monetisable intermediary has faced the same treatment. Email survived because it was too entrenched to kill, though Google and Microsoft have done their best to centralise it through Gmail and Outlook’s dominance. The web itself survived because HTTP was already universal before the advertising platforms reached their current scale. But every new protocol that emerges now does so in the shadow of companies that will oppose it if it threatens their position as intermediary. ActivityPub, AT Protocol, Nostr, and Matrix are all fighting the same fight that RSS lost.

What should you do? If you have never used an RSS reader, start. Pick a reader — Feedbin if you want a hosted service with a good web interface, NetNewsWire if you use a Mac and want a native app, Miniflux if you have a server and want something minimal and fast. Subscribe to the blogs and news sites you actually want to read. Delete the algorithmic news apps from your phone. The transition takes an afternoon and improves your information diet permanently. You will read less but better. You will be less angry and more informed. You will spend your attention on what you chose rather than what an engagement algorithm chose for you.

If you publish content, publish an RSS feed. If yours does not, an RSS feed is literally an XML file that you can write by hand. Make sure your feed contains the full content of your posts, not just summaries, because reading in an RSS reader should not require clicking through to a website. If your business model requires page views and advertisements, include a brief summary in the feed and link to the full article. But do not abandon the protocol just because the intermediaries want you to.

The closure of Google Reader was not a product retirement. It was a strategic decision to remove an alternative distribution mechanism that competed with Google’s own advertising-driven content surfaces, and it worked. RSS did not die because users stopped wanting it. It died because the company that controlled the dominant reader decided that users wanting it was the problem. The protocol itself is fine. It has been fine for over two decades, and it will be fine for two more. The question is whether enough people will choose the open protocol over the algorithmic feed to make a difference. If you are tired of being told what to read by machines that are paid to keep you scrolling, this is where you start.