There is a particular kind of quiet that settles over a project when its founder decides to walk away. In October 2025, Andrew Dolgov a developer known online as "fox" chose that silence. He posted a brief statement explaining that on November 1st of that year, he would dismantle the infrastructure powering tt-rss.org, including its Git repositories, cgit instance, and user forum. The message was characteristic: direct, unsentimental, and final.
"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 platforms, the death of Google Reader in 2013, and the countless small maintenance tasks that accumulate invisibly around any living piece of software. Twenty years of answering forum questions, fixing compatibility issues, updating dependencies, and keeping a door open for anyone who wanted to read the web on their own terms.
The announcement could have been an ending. Instead, it became a handoff.
The Volunteer Who Stepped Forward
Before November 1st arrived, a new maintainer had already stepped in. Ownership of the tt-rss.org domain transferred. The site began redirecting visitors to a new GitHub repository where ongoing development continues under a fork of the original project. The software itself Tiny Tiny RSS, or TT-RSS did not die.
This is the part of the story that matters most, not just for developers who use RSS readers but for anyone who thinks about how digital infrastructure survives. Open-source projects live and die by maintainer attention. A single person, or a small team, carries the weight of decisions, bug reports, compatibility updates, and the thousand small negotiations that keep a project usable. When that person burns out and burnout is common in open-source, where contributions are often unpaid and invisible the project can simply disappear.
What happened with TT-RSS was different. Someone saw the announcement and chose to act. They took ownership of the domain, set up the redirect, and committed publicly to keeping the project alive. They promised to update TT-RSS to support newer PHP versions and to handle bug fixes as they arise. The work continues, even though the original architect has stepped back.
The Linuxiac report noted that "users who rely on self-hosted RSS aggregation won't need to worry about the tool disappearing." That sentence carries more weight than it might first appear. For twenty years, TT-RSS gave people a way to read the web that belonged to them a reader they controlled, feeds they chose, no algorithm deciding what they saw or when.
What RSS Actually Is and Why It Still Works
RSS, which stands for Really Simple Syndication, is a standardized XML format for publishing frequently updated content. A website that publishes an RSS feed provides a machine-readable document listing recent content: titles, publication dates, summaries or full text, and links to the originals. Feed readers applications like NetNewsWire, Feedly, Reeder, Inoreader, and Miniflux subscribe to these feeds and aggregate content from multiple sources into a unified reading interface.
The appeal is straightforward: instead of visiting twenty publications separately to check for new content, a reader checks one application that has already fetched everything. But the deeper value lies in what RSS does not do.
RSS is platform-independent and publisher-controlled. A reader who subscribes to an RSS feed gets content directly, without any algorithmic intermediary deciding what they see or how it is prioritized. This distinction has become increasingly significant as social media platforms have matured. As a Publishing House analysis from April 2026 observed, "The social media era was supposed to replace RSS. It did reduce its mainstream use. It also created algorithmic mediation of content distribution your audience sees what the platform decides to show them, in an order determined by engagement optimization, not publication time or reader preference."
The analysis continues: "Publishers who built their distribution strategy entirely around social media have experienced this directly. Algorithm changes, account suspensions, reach throttling, and platform decline have repeatedly cut publishers off from audiences they spent years developing."
RSS is the opposite of this. A subscriber to an RSS feed sees every post published, in the order they were published, in a reader they control. There is no algorithm, no engagement optimization, no platform that can decide tomorrow to reduce organic reach. The relationship between publication and reader is direct.
The Audience That Never Left
The RSS audience is not large by social media standards. But it is specific and valuable. As the Publishing House analysis notes, RSS users tend to be "technically literate, actively interested in following publications more than passively scrolling, and typically more engaged with content than the average social media follower." Developers, journalists, researchers, academics, and serious readers in every field disproportionately use RSS.
For publications targeting these audiences technology, science, finance, policy, professional media an RSS feed is often the preferred consumption channel for a meaningful portion of the readership. These are the people who notice when a feed breaks, who care about proper formatting, who subscribe to feeds from individual authors beyond just site-wide aggregators.
This is the audience that kept TT-RSS alive for twenty years. They are the reason someone stepped forward when Dolgov announced he was stepping back. They are the reason that Tiny Tiny RSS now maintained by new hands continues to exist as an option for anyone who wants to run their own feed reader on their own server.
The transition also illustrates a quieter truth about open-source sustainability. The popular narrative around open-source often focuses on creators: the brilliant developer who starts a project, the visionary who builds a community. Less visible is the work of maintenance the ongoing, unglamorous labor of keeping something running year after year. This work is often done by a single person or a small group who may receive little recognition and no pay.
Dolgov's twenty years of maintenance were, as the Linuxiac report acknowledges, "dedicated" and deserving of "respect and appreciation." The new maintainer's decision to step in represents a different kind of dedication: the choice to inherit a project, to carry its history forward, to do the unglamorous work of maintenance because the tool matters to the people who use it.
Why This Matters for PostsNews Readers
For readers researching publishing, media, and news aggregation, the TT-RSS story offers several practical lessons. First, it demonstrates that RSS infrastructure is more resilient than it might appear. When Google Reader shut down in 2013, many observers predicted RSS would fade away entirely. Instead, it persisted. Self-hosted solutions like TT-RSS continued to function. New readers emerged. Publishers who valued direct audience relationships maintained their feeds.
Second, the story reveals how open-source stewardship actually works. When a project matters to its users, someone will often step forward to maintain it. This is not guaranteed many open-source projects do disappear when their maintainers burn out but it happens often enough that choosing open-source tools with active communities can be a form of risk management. The TT-RSS transition shows that self-hosting, while requiring more technical involvement than using a third-party service, also means your reading infrastructure does not depend on any single company's business decisions.
Third, for publishers considering where to invest their distribution efforts, RSS offers something increasingly rare: guaranteed reach to a self-selected audience. As algorithmic platforms continue to restrict organic reach and introduce fees for visibility, RSS provides a distribution channel that belongs entirely to the publisher. Every subscriber who adds your RSS feed will see your content, in the order you published it, with no intermediary deciding otherwise.
The Publishing House analysis makes this explicit: "The key characteristic of RSS is that it is platform-independent and publisher-controlled." In an era when distribution relationships with social platforms carry significant risks risks that have materialized repeatedly as platforms change their policies, get acquired, or shut down entirely RSS represents a form of insurance that costs nothing and relies on no one's goodwill except your own.
The Shape of What Comes Next
The new TT-RSS maintainer faces real challenges. The software was described by Dolgov as "done" meaning it had reached a state of functional completeness where new features were not the priority. The ongoing work is maintenance: updating to newer PHP versions, fixing breakages, responding to bug reports from users. This is essential but often invisible work.
PHP, the programming language TT-RSS is built on, continues to evolve. Each new major version brings changes that can break compatibility with older code. Keeping TT-RSS current with PHP versions means ongoing effort, even if the core functionality remains stable. The new maintainer has committed to this work, but the open-source ecosystem has seen many projects stagnate when maintainer attention wanes.
What seems clear is that the TT-RSS community intends to resist that stagnation. The domain transfer, the GitHub repository, the public commitment to continued development these are concrete steps, not just optimistic statements. For a project that has already survived the death of Google Reader and the broader decline of RSS from mainstream consciousness, these are not small things.
Meanwhile, RSS itself continues to evolve in relevance. The Publishing House analysis, written in April 2026, argues that "RSS is not only not dead for certain audiences and publishing contexts, it is more relevant than it has been in a decade." This is partly a reaction to the volatility of social media platforms and partly a reflection of growing awareness among publishers about the value of direct audience relationships.
The tools for RSS publishing are mature and well-documented. Most content management systems generate RSS feeds automatically. WordPress generates feeds at /feed/ by default, with separate feeds for every category, tag, and author. Hugo generates an RSS feed at /index.xml from any section with content. Ghost publishes feeds automatically. Adding RSS to a website is rarely a technical challenge; the question is whether publishers recognize its value.
A Timeline of the TT-RSS Transition
| Date | Event |
|---|---|
| August 2005 | Andrew Dolgov launches Tiny Tiny RSS |
| 2013 | Google Reader shuts down; RSS survives through alternatives like TT-RSS |
| October 11, 2025 | Linuxiac reports Dolgov's announcement that TT-RSS infrastructure will shut down on November 1, 2025 |
| November 1, 2025 | Original tt-rss.org infrastructure dismantled; new maintainer takes over |
| Post-November 2025 | Domain ownership transferred; site redirects to new GitHub repository; ongoing development continues under fork |
| April 2026 | Publishing House publishes analysis confirming RSS remains relevant for publishers |
Where to Read Further
For readers who want to explore the TT-RSS story and RSS ecosystem more deeply, the following resources provide additional context:
- The Linuxiac report on the TT-RSS shutdown and transition covers Dolgov's announcement, the new maintainer's takeover, and the project's twenty-year history in detail.
- The Publishing House analysis of RSS relevance in 2026 explains why publishers should care about RSS, who uses it, and how to add it to a publication's distribution strategy.
- The regex101 tool offers a reference for the regular expression syntax that underpins RSS feed parsing and XML processing, useful for developers working with feed formats.
- The new TT-RSS GitHub repository (linked from the Linuxiac report) is where ongoing development continues under the new maintainer.
The Work That Continues
Open-source maintenance is often described as invisible work. The user sees a working tool; they do not see the hours spent updating dependencies, answering forum questions, reviewing bug reports, and making the small decisions that keep a project coherent over years and decades. Dolgov did this work for twenty years. Someone else is doing it now.
For the readers who depend on TT-RSS who have built their daily reading practice around its interface, who have configured their own servers to run it, who have written plugins and shared tips in its forum this continuity matters. The tool will keep working. The feeds will keep updating. The inbox of unread articles will keep filling each morning.
And for publishers who have maintained RSS feeds through the rise and fall of platforms, through algorithm changes and account suspensions, through the constant churn of distribution channels that promised permanence and delivered volatility, the TT-RSS story offers a quiet reassurance. The infrastructure for direct reader relationships still exists. It still works. And sometimes, when the original creator steps away, someone else steps in to keep the door open.
That is not nothing. In a media landscape increasingly defined by dependence on platforms that do not belong to you, the existence of tools you control readers you run, feeds you publish, relationships you maintain directly is a form of freedom. Small, unglamorous, and worth protecting.