Most assumed the death of tt-rss.org, a popular self-hosted RSS reader, was a natural consequence of declining interest in RSS itself. But when developer Andrew Dolgov, known as “fox,” announced its shutdown in October 2025, it wasn't a slow fade it was a deliberate dismantling of infrastructure, repositories, and community forum. This abrupt act sparked not resignation, but a surprising surge of volunteer effort to keep the open-source project alive.
"The reasons for this are many but the tl;dr is that I no longer find it fun to maintain public-facing anything, be it open source projects or websites," Dolgov wrote, according to a report from Linuxiac published on October 11, 2025. "As for tt-rss specifically, it has been 'done' for years now and the 'let's bump base PHP version and fix breakages' routine is not engaging in the slightest."
Twenty years. That is how long Dolgov had carried Tiny Tiny RSS a self-hosted, open-source RSS reader and news aggregator from its launch in August 2005 through the rise and fall of Google Reader, through the mobile web revolution, through the great social media migration and return. He had kept it running, updated, and meaningful through two decades of shifting internet tides.
And then, on the eve of its twentieth anniversary, he was ready to let it go.
The Weight of Twenty Years
Tiny Tiny RSS is a web application that must be installed on a web server, allowing users to run their own feed reading infrastructure on their own hardware. Following Google's 2013 announcement that they would be retiring Google Reader, Tiny Tiny RSS was widely reviewed as a possible replacement in major tech blogs and online magazines. Reviewers praised its versatility while noting that its performance and installation process presented challenges for less technical users.
The project was written in PHP and released under the GPL-2.0 license initially, later updated to GPL-3.0-or-later. It supported multiple database backends and offered a plugin system that extended its functionality. For power users who wanted complete control over their reading experience who distrusted cloud services, who wanted to host everything themselves Tiny Tiny RSS was a quiet staple.
But open-source software has a human problem that code cannot solve. The question is not whether the software works. The question is whether anyone will keep maintaining it.
Dolgov had been asking himself that question for years, it seems. The announcement in October 2025 was not dramatic. There was no confrontation, no controversy. Just a developer who had given two decades to a project and finally reached the edge of his willingness to continue.
The Volunteer Who Stepped Forward
What happened next was unusual not because it never happens in open source, but because of how quietly and completely it happened. Before the November 1, 2025 shutdown date arrived, a new volunteer maintainer stepped forward to carry the work forward.
The tt-rss.org domain was transferred to this new maintainer, and the site began redirecting to a new GitHub repository where ongoing development continues under a fork of the original project. The transition was seamless enough that many users may not have noticed the change in ownership at all.
This kind of volunteer succession is a defining feature of the open-source RSS ecosystem. Unlike venture-backed startups, where a shutdown often means permanent deletion consider Pocket, which ran from 2007 to 2025 before shutting down eighteen years of saved articles, or Omnivore, which served 500,000 or more users from 2023 to 2024 before being acqui-hired and shut down open-source projects can survive their original creators because the code belongs to everyone.
When Dolgov walked away, Tiny Tiny RSS did not disappear. It simply changed hands.
The Economics of Free Software
To understand why this matters, it helps to understand the economics at play. The RSS reader market in 2026 looks substantially different from what it did even two years prior. Several notable cloud-based services have shuttered or been acquired. Meanwhile, RSS adoption surged 34% year-over-year among professionals, driven by anyone fed up with algorithmic timelines deciding what they see.
The tools that survived and the new ones that emerged have splintered into radically different philosophies. Some bet heavily on AI-assisted reading. Others reject it entirely. Some aim to be comprehensive knowledge management systems. Others simply want to display a clean list of headlines.
What distinguishes the self-hosted RSS readers Tiny Tiny RSS among them is their economic model. They are free and open source. There are no subscription fees, no data mining, no venture capital expectations of exponential growth. Your only cost is the server that runs it, which can be a modest virtual private server, a Raspberry Pi at home, or the same machine hosting your other services.
This creates a fundamentally different relationship between the tool and its users. When a venture-backed service shuts down, users lose everything their reading history, their saved articles, their carefully curated source lists. When a self-hosted reader's developer steps away, the community can catch the project. The server keeps running. The feeds keep updating. The software keeps improving, just under different hands.
The Self-Hosted Landscape in 2026
Three self-hosted RSS readers have emerged as the primary options for users who want to run their own infrastructure in 2026. Each represents a different philosophy about what a feed reader should be.
FreshRSS positions itself as the best all-around choice. Built in PHP, it supports SQLite, MySQL, or PostgreSQL databases, runs on low to moderate resources (50-150 MB RAM), and offers a full-featured, modern web interface. It includes a plugin system and multi-user support, and it works well with the Fever API for mobile access through apps like Reeder and NetNewsWire.
Miniflux takes the minimalist approach. Written in Go, it uses only PostgreSQL and consumes ultra-low resources (10-30 MB RAM). Its interface is intentionally minimal and keyboard-driven, with native apps for iOS and Android. There is no plugin system by design, the developers argue that simplicity is a feature.
Tiny Tiny RSS, the long-running project now under new stewardship, remains the power user's choice. Also written in PHP, it requires moderate resources (100-250 MB RAM) but offers a feature-rich, customizable interface and a mature plugin ecosystem. Its strength has always been its flexibility the ability to bend it to your specific workflow.
These three tools share a common economic reality: they are free to use, free to modify, and free to redistribute. Their development is sustained not by investor expectations but by community engagement, volunteer effort, and the intrinsic motivation of developers who care about the problem.
The case for self-hosting an RSS reader comes down to four pillars: privacy, permanence, control, and cost. Cloud-based services track what you read, how long you spend on each article, and which topics interest you most. That data has value and it is not yours. A self-hosted reader keeps every interaction on your own server. When you self-host, the service lives as long as your server runs. No corporate decisions can take it away.
Why RSS Still Matters
RSS which stands for Really Simple Syndication is a standardized XML format for publishing frequently updated content. It remains relevant because it is platform-independent and publisher-controlled. Subscribers see every post in the order published, with no algorithm mediating what they see.
For publishers tired of algorithmic distribution changes on social platforms, RSS offers a direct relationship with readers that no platform decision can interrupt. You publish once; your subscribers receive it directly. There is no algorithm deciding whether to surface your work, no feed ranking that buries older content, no advertising model that incentivizes engagement over quality.
The protocol has also become the invisible backbone of podcasting. Every podcast app Spotify, Apple Podcasts, Pocket Casts subscribes to shows via RSS feeds. A creator publishes once; every platform picks it up automatically, without negotiating distribution deals. This is one of the most successful deployments of RSS in history, and it happens entirely in the background.
Most podcast listeners have no idea they are using it.
The Quiet Renaissance
In 2026, RSS is consolidating into something more durable: the preferred tool for a specific kind of reader professionals, researchers, and anyone who has decided that algorithmic feeds are no longer serving them. The historical weakness of RSS was volume. Following fifty sources can mean hundreds of articles a day more than any person can read.
AI aggregators address this directly. Tools like Brief Digest group related stories from multiple sources, generate short summaries, and filter noise automatically. You follow more sources but spend less time. The combination of human source choices and AI-assisted reading is drawing a new generation of users back to RSS.
RSS in 2026 is not for everyone and that is fine. It is for people who read with intention. The combination of full source control, privacy by default, and tools that handle volume makes it more capable than it has ever been.
The Human Infrastructure of Open Source
The story of Tiny Tiny RSS is ultimately a story about the human infrastructure of open source. Software projects do not survive on code alone. They survive because someone, somewhere, cares enough to keep them alive.
Dolgov cared for twenty years. He updated PHP versions, fixed breakages, responded to support requests, and maintained the infrastructure that thousands of people relied on every day. That labor was invisible to most users and unsponsored by any corporation. It was sustained by whatever motivates a developer to keep working on something past the point of novelty.
When he decided he was done, another person stepped forward. Not because they were paid to. Not because they were contracted to. Simply because they cared, and because the nature of open source meant they could.
This is the quiet economics of RSS: no funding rounds, no acquisition talks, no board meetings, no investor pressure to grow or pivot or sell. Just code that belongs to everyone, and humans willing to tend it.
What This Means for PostsNews Readers
For readers researching sustainable publishing tools and independent media infrastructure, the Tiny Tiny RSS story illustrates a model worth understanding. Open-source RSS readers demonstrate that viable information technology does not require venture capital. Longevity in this space depends less on funding and more on community care on users who are willing to contribute, maintain, and sustain the tools they rely on.
If you publish content online, your CMS likely generates an RSS feed automatically. WordPress creates feeds at /feed/ by default, with separate feeds for each category, tag, and author. Hugo generates feeds at /index.xml from content sections. Ghost publishes feeds automatically. Ensuring your feed URL is discoverable connects you directly to readers who have chosen to follow your work without algorithmic intermediation.
The volunteers who maintain these projects are not building the next unicorn. They are building something more durable: infrastructure that belongs to its users, controlled by no single entity, and capable of outlasting any individual contributor's attention.
Where to Read Further
The transition of Tiny Tiny RSS from solo developer to community project is documented in depth in the PostsNews Research Desk coverage of the event, which traces the October 2025 announcement through the volunteer succession. For a technical comparison of the current self-hosted RSS landscape, the Pi Stack comparison of FreshRSS, Miniflux, and Tiny Tiny RSS provides detailed specifications across resource usage, features, and deployment options. To understand the broader 2026 trends driving professionals back to RSS, the Brief Digest analysis of RSS's quiet renaissance maps the five key patterns shaping the protocol's renewed relevance.
For readers interested in the broader bootstrapping context how independent projects sustain themselves without venture capital the IMFounder coverage of bootstrapped startups in 2026 offers perspective on non-traditional funding models in the technology sector.
| Self-Hosted RSS Reader | Language | Resource Usage | Best For |
|---|---|---|---|
| FreshRSS | PHP | 50-150 MB RAM | Most users, feature-rich experience |
| Miniflux | Go | 10-30 MB RAM | Minimalists, low-resource setups |
| Tiny Tiny RSS | PHP | 100-250 MB RAM | Power users, customizable workflows |
The volunteer who caught Tiny Tiny RSS when it fell did not make headlines. There was no press release, no launch event, no funding announcement. They simply picked up the project and kept it going because that is what the community does when something matters enough to save.