Chaos and Order

💡 왼쪽 원문을 읽으면서 오른쪽에 따라 써보세요. Tab 키로 힌트를 받을 수 있습니다.

원문 렌더가 준비되기 전까지 텍스트 가이드로 표시합니다.

Prologue — the summer Pocket disappeared, and what came after

In May 2025 Mozilla announced that Pocket would shut down on July 8. Half of the internet stirred. Pocket had started in 2007 as Read It Later, was acquired by Mozilla in 2017, and was effectively the founder of the read-later category. Tens of millions of casual users came along for the ride thanks to the Firefox integration and a generous free tier. It ended with one short notice.

A quieter event had happened earlier on the other side. In October 2024 Omnivore stopped operating. It was an open source, self-hostable rising star in the read-later space. The core team joined ElevenLabs and the project died of natural causes. Earlier that spring, Read.cv had also shut down after Perplexity acquired it. Matter survived but changed its pricing model and became a little heavier; Readwise Reader quickly filled the vacuum.

That is not the whole story. On the RSS side, the signals were the opposite. Silvio Rizzi started shipping a brand-new app called Reeder (the 2025 model) alongside continued maintenance of Reeder 5. NetNewsWire kept polishing its 6.x line as the truly free open source option. Inoreader doubled down on pro features and Feedly went deeper on its Leo AI. On the self-hosting side, Miniflux 2 and FreshRSS entered a quiet stable phase. RSS was declared dead at least once before, in 2013 when Google Reader shut down, but thirteen years later the ecosystem is more diverse and more stable than ever.

This article maps that landscape end to end. We compare seventeen tools on the same axes and finish with a four-way "what should you pick" guide. Prices in this article are as of May 2026 and change often, so verify on the official site before deciding.

> Number of times RSS has been declared dead: at least five. Number of times it has actually died: zero.

1. The 2026 RSS revival — the landscape after Pocket shut down (July 2025)

Where did Pocket users go in the summer of 2025? Anecdotally and from Readwise Readers own announcements, their user base roughly quadrupled in June through August of that year. Matter saw a similar surge. Karakeep (formerly Hoarder) doubled its GitHub stars within two months and earned the badge of "the open source alternative." Wallabag also grew, in a smaller wave. Instapaper barely moved — it had been stagnant for years after the Pinterest spin-off, and the Pocket shutdown news did not move it much.

The RSS reader side was more interesting. A meaningful chunk of Pocket users decided "while I am at it, let me also leave the algorithmic feed." New signups went up at the same time at Reeder, NetNewsWire, Inoreader, and Feedly. Even Feedbin, a paid-only service, doubled its trial signups. Self-hosting guides for Miniflux and FreshRSS hit the Hacker News front page again. In Korea, blog posts reminiscing about the late Daum RSS Reader were going around again. Strange parade.

Why did RSS survive? Algorithm fatigue. X (Twitter) lost trust in its recommendation algorithm years ago; Threads pulled people in with novelty but failed to keep them; LinkedIn is a work-only space for most. Eventually the old RSS promise — "I decide what I read and where" — became attractive again. The LLM era added one more variable: people now want to curate their information diet themselves, not handing it to algorithms and not handing it to an AI either. RSS is the best-fitting tool for that desire.

2. How RSS survived — life after Google Reader (2013)

On July 1 2013, Google Reader shut down. At the time it was effectively the default backend for RSS — nearly every client used Google Readers sync API. The moment the shutdown was announced, obituaries for RSS came in waves and many people accepted them.

Paradoxically, that event triggered a **diversification of providers** in the RSS ecosystem. Feedly moved quickly to take the Google Reader replacement slot. Feedbin, NewsBlur, and The Old Reader grew in earnest. Reeder expanded its own sync backend options. NetNewsWire, which had been quiet for years, restarted development. Inoreader appeared from Bulgaria and grew fast. By 2014 there were more RSS clients and more sync backends than there had been in June 2013.

The self-hosting side gained energy at the same time. Tiny Tiny RSS had been around, but its user base grew. FreshRSS was born in 2013 to 2014, written in PHP. Miniflux launched in 2014 in Go and became synonymous with "simple and fast." Long before the term "selfhosted" became trendy, RSS had been a model citizen for self-hosting.

Looking at 2026 thirteen years later, **the era of depending on a single provider (Google Reader) is over**, and RSS has become a small but very pluralistic ecosystem. Pocket can disappear and Readwise or Matter takes the load; Omnivore can disappear and Karakeep or Wallabag takes the load. RSS is a decentralized protocol at heart, so even when one company dies, your data comes out in one OPML file and you can migrate everywhere. That simplicity is the real survival secret.

3. Reeder 5 + Reeder (25) — Silvio Rizzis new app

Reeder, built by Silvio Rizzi, is the design benchmark for macOS and iOS RSS clients. In 2026, the interesting fact is that Reeder runs as two apps in parallel — **Reeder 5** (now sometimes called "Classic") and **Reeder (the 2025 model, often labeled "Reeder New")**.

**Reeder 5 (Classic)**

The fifth generation, released in 2021. Paid one-time purchase, roughly USD 15 on macOS and USD 5 on iOS, varying with currency. Traditional three-pane design with folders, subscription tree, article list, and content. Supports almost every backend — Feedbin, Feedly, Inoreader, Miniflux, FreshRSS, NewsBlur, iCloud, local. Its strength is unchanging stability. Silvio has said he will not kill 5 and will keep maintaining it for security and OS compatibility.

**Reeder (25, the new Reeder)**

A completely new app from 2024. The design philosophy is different — the **timeline view** is central. The concept is to see every source as a single chronological stream. Beyond RSS it can mix in Mastodon, Bluesky, YouTube, and podcasts on the same timeline. iCloud handles cross-device sync. Pricing is a subscription — roughly USD 1 per month or USD 10 per year. Some users described it as "no longer an RSS reader but an info-aquarium."

**Which one should you pick**

If you love a traditional folder, unread count, starred workflow then Reeder 5 is your answer. If you prefer to let every source flow by chronologically and skim what catches your eye, pick the new Reeder. The two apps can run against the same data (Feedbin or Inoreader account) so you can install both and compare.

4. NetNewsWire — open source free for Mac and iOS

NetNewsWire is the history of RSS clients itself. Brent Simmons originally built it in 2002, the project changed hands several times, and Brent eventually brought it back as open source (MIT). Free on macOS, iOS, and iPadOS. No ads, no subscription.

**Tech stack and sync**

Written in Swift, supports macOS 13+ and iOS 16+. There is no native sync backend, but it talks to Feedbin, Feedly, Inoreader, iCloud, BazQux, FreshRSS, NewsBlur, and more. Local data lives in SQLite. iCloud sync is a free option that works well enough for almost everyone.

**Design philosophy**

Extremely conservative. Three-pane design, keyboard shortcut driven, no algorithm of any kind. It has ad blocking and article body extraction, but no AI or recommendation features at all. The position is "an RSS reader does the job of an RSS reader." That is suffocating for some and heaven for others.

**Community and roadmap**

Actively developed on GitHub. As of May 2026 the stable line is 6.x, with a 7.0 beta running for iOS. Contributor count has stayed above a healthy threshold, so the risk of single-maintainer collapse is relatively low.

**Weaknesses**

No Windows or Linux. Apple ecosystem only. iCloud sync can occasionally lag. Mobile notification features are limited.

5. Inoreader — strongest for pros

Inoreader is a web-based RSS service built by Innologica in Bulgaria since 2013. The free tier is quite generous (up to 150 sources) and the paid Pro tier runs around USD 9.99 per month. The free tier has ads but they are bearable.

**Why "strongest for pros"**

Feature depth is different. Keyword monitoring (get alerted when a word appears in any feed), rule-based auto categorization and tagging and highlighting, global search across all your past articles (full text), newsletter receiving (Inoreader gives you an email address; subscribe with it and the newsletter becomes RSS), Reddit, X, Bluesky, YouTube and podcasts as RSS-like sources, team collaboration with shared folders. That is why journalists, researchers, and competitive analysts love it.

**Mobile and desktop**

Native iOS and Android apps, and a well-built PWA on the web. Compatible with external clients (Reeder, Fluent Reader, and others). Desktop is web-first but an Electron app exists.

**Weaknesses**

The UI is slightly complex. Free users see a few ads. The Pro price is on the higher end of the spectrum — roughly USD 100 per year. For true heavy users though, it is worth it.

6. Feedbin — the classic paid option

Feedbin is a paid web-based RSS service built by Ben Ubois since 2013. Pricing is simple — USD 5 per month or USD 50 per year. There is no free tier, only a 30-day trial.

**Why people love Feedbin**

Minimalism. Zero ads, zero algorithm, zero AI. Just a clean RSS reader. Newsletter receiving (like Inoreader, an assigned email), Twitter/X and YouTube as RSS, a native iOS app, and excellent compatibility with external clients (Reeder, NetNewsWire, every well-built third party). The Feedbin API has effectively become one of the standard sync protocols.

**Technical reliability**

It has run stably for over ten years despite being mostly a one-person operation. Almost no downtime, well-thought-out background features like backups and email digests. The model citizen of "trusted SaaS by an independent developer."

**Weaknesses**

The price is on the higher side — at a time when many free options exist, USD 5 per month is a real ask for casual users. Pro-style features like keyword monitoring and rules are absent or weak. The UI is so simple it feels feature-poor at first, but that is the selling point.

7. Feedly (Leo AI) — the former king

Feedly launched in 2008 and became the de facto market leader after Google Readers 2013 shutdown brought a flood of users. In 2026 Feedly is no longer "the best personal RSS reader" but still has a massive user base, and it is pivoting to the enterprise market with **Leo AI** as its weapon for AI curation.

**Free, Pro, Enterprise**

Free covers up to 100 sources. Pro is USD 6 per month or USD 60 per year. Pro+ is USD 12 per month and adds AI features like Leo. The Enterprise tier is unpriced publicly and is specialized for Threat Intelligence — that is the core of Feedlys revenue.

**Leo AI**

An AI that filters feeds with natural-language rules. Examples: "show me only news about this company," "only mergers and acquisitions," "only CVEs with published PoC code." Available on Pro+ and above.

**Weaknesses**

Free and Pro users feel increasingly de-prioritized. The UI is heavy, the mobile app shows ads, and for users who just want "clean RSS" it is no longer the first pick. But for security and intelligence teams, Leo is genuinely compelling.

8. Miniflux — Go for self-hosting

Miniflux is a self-hosted RSS reader Frédéric Guillot has been building in Go since 2014. As of May 2026 the stable line is 2.x. Licensed under Apache-2.0. The definition of true minimalism.

**Design philosophy**

Intentionally feature-poor. No ads, no recommendations, no keyword alerts. It does the essence of an RSS reader, nothing more. The UI is text-first and minimal. It runs fine as a PWA on mobile.

**Tech stack**

Single binary Go application. PostgreSQL on the backend. A single Docker line spins it up. It runs on 100-200 MB of memory, so a Raspberry Pi or a small VPS is enough. It exposes Fever and Google Reader compatible APIs so external clients like Reeder and NetNewsWire connect cleanly.

**Install example**

version: "3"

services:

miniflux:

image: miniflux/miniflux:latest

ports:

- "8080:8080"

depends_on:

- db

environment:

- DATABASE_URL=postgres://miniflux:secret@db/miniflux?sslmode=disable

- RUN_MIGRATIONS=1

- CREATE_ADMIN=1

- ADMIN_USERNAME=admin

- ADMIN_PASSWORD=changeme

db:

image: postgres:16-alpine

environment:

- POSTGRES_USER=miniflux

- POSTGRES_PASSWORD=secret

volumes:

- miniflux-db:/var/lib/postgresql/data

volumes:

miniflux-db:

**Weaknesses**

It can feel too sparse. No native newsletter receiving — you have to run your own email gateway. Mobile push notifications require pairing with something external like ntfy.

9. FreshRSS — PHP for self-hosting

FreshRSS is an open source RSS reader written in PHP, born in 2013 to 2014. In 2026 it is the most popular PHP-based self-hosted RSS option. Licensed under AGPL-3.0.

**Design philosophy**

Richer in features than Miniflux. Categories, tags, filters, statistics, webhooks, OPML import and export, and multi-protocol APIs (Fever, GReader, Google Reader compatible) all built in. The UI feels a little dated but is stable.

**Tech stack**

PHP 8.x with SQLite, MySQL, or PostgreSQL. It installs even on shared hosting, which is a major advantage — anyone used to Hostinger, NameCheap, or DreamHost-style PHP hosting feels at home. The official Docker image exists too.

**Extensions**

There is an extension system that lets you plug in lightweight add-ons. Ad blocking, dark mode variants, and article body extraction (via a Mercury Parser backend) are common.

**Weaknesses**

Being PHP, security patch hygiene is something to mind. The UI can feel a bit cramped on mobile. The recommended mobile path is an external client (Reeder, FluentReader, and so on) connected via the GReader API.

10. Tiny Tiny RSS / NewsBlur — the other self-hosted options

**Tiny Tiny RSS (TT-RSS)**

Andrew Dolgov has been building TT-RSS in PHP since 2005. It was once the de facto standard for self-hosted RSS. By 2026 it has lost a lot of mindshare to FreshRSS and Miniflux. Licensed under GPL. The maintainer has strong opinions, especially about user support policy, that divide people. Stability and feature depth are still solid.

**NewsBlur**

Samuel Clay runs NewsBlur as a SaaS (web and mobile apps) but the code is open source (MIT), so self-hosting is possible. Self-hosting installs via Docker Compose. The system is fairly heavy — MongoDB, Redis, and PostgreSQL are all required. A small VPS may struggle.

NewsBlurs signature is the **Intelligence Trainer** — you teach it the keywords, authors, and tags you like or dislike, and it scores recommendations. It is a pre-AI-era recommender system but it works. The SaaS is free up to 64 sites or USD 36 per year for Premium. Honest pricing.

**TT-RSS vs FreshRSS vs Miniflux vs NewsBlur self-host comparison**

|---|---|---|---|---|

| Language | Go | PHP | PHP | Python |

Want a small VPS install → Miniflux. Comfortable with PHP and want some features → FreshRSS. Seasoned self-hoster with a settled workflow → TT-RSS. Like the option to use SaaS and self-host → NewsBlur.

11. Pocket sunset (July 2025) — how users moved

Pockets exact timeline was: new signups closed on May 22 2025, full shutdown on July 8 2025, and permanent user data deletion on October 8 2025. Mozilla provided an OPML/CSV export tool that produced bookmark URLs and additional metadata.

**Migration patterns (June to December 2025)**

These are informal observations but the major flows were:

1. **To Readwise Reader**: the biggest flow. Paid (roughly USD 10 per month) but powerful highlights, sync, RSS, and email integration. The natural path for existing Readwise users.

2. **To Matter**: good design and a free tier made it the popular casual destination. Matter later changed its pricing slightly and got a little heavier, but stayed popular.

3. **To Instapaper**: the oldest alternative, with a free tier and a familiar UI. Stagnant feature-wise, but for many users that was fine.

4. **To Karakeep (formerly Hoarder)**: for those who wanted an open source self-hostable option. Tech-savvy crowd.

5. **To Wallabag**: for users who liked the combination of open source, self-host, and SaaS options.

6. **Folded into RSS**: a chunk of users abandoned the "read later" concept entirely and consolidated into the star feature of their RSS reader. One reason Reeder, NetNewsWire, and Inoreader signups grew.

**The real Pocket lesson**

Even a company like Mozilla can shut down an acquired product. If you want control over your own data, the **open source + self-hosted + standard format** combination is safest. Next is a SaaS that exports cleanly to OPML/CSV/JSON. The worst is a SaaS that locks your data in a closed format.

12. Readwise Reader / Matter — the new wave of read-later

**Readwise Reader**

Built by Readwise, the highlight-sync service founded in 2019, Reader launched in 2022 as a full-stack reading app. In 2026 it is effectively the top-tier option in the read-later category. Roughly USD 10 per month (USD 9.99/month) or USD 100 per year (USD 99.99/year).

Features: RSS reader, web clipper, PDF reader, EPUB reader, YouTube transcripts, email newsletter inbox, AI highlights and summaries (Ghostreader), TTS, and Readwise sync that automatically dumps highlights into Roam, Obsidian, Notion, and Logseq.

The strength is **integration** — a single app handles RSS, read-later, and book notes. The weaknesses are price and a slightly heavy UI.

**Matter**

Swedish origin, launched in 2021. Free during the beta and went paid around 2024. Roughly USD 8 per month or USD 60-70 per year. Some free tier still exists (basic reading is free, advanced features are paid).

Characteristics: excellent TTS quality (voices feel natural by many accounts). Clean design, especially polished on mobile. Newsletter receiving, highlights, graph view. Some RSS support too.

**Readwise Reader vs Matter**

| Aspect | Readwise Reader | Matter |

|---|---|---|

| Price per month | About USD 10 | About USD 8 (free tier exists) |

| RSS | Strong | Moderate |

| PDF/EPUB | Strong | Moderate |

| TTS | Good | Very good |

| Highlight sync | Strong (Roam/Obsidian/Notion etc.) | Moderate |

| Design | Functional | Minimal and elegant |

| Mobile experience | Good | Very good |

Want deep integration with knowledge notes (Obsidian, etc.) and to handle RSS, PDF, and YouTube in one place → Readwise. Want a clean mobile read and a TTS that you can listen to on a walk → Matter.

13. Karakeep (formerly Hoarder) — open source bookmarks + read-later

Karakeep started in 2023 as Hoarder, an open source bookmark + read-later app. In 2025 a trademark and naming issue caused the rename to Karakeep. Licensed under AGPL-3.0. Written in TypeScript on top of Next.js.

**Features**

Save a web page, auto-extract the body, auto-tag (clustering via embeddings), AI summaries (LLM API key required), full-text search, and RSS feed ingestion. iOS and Android apps and a web clipper extension exist.

**Tech stack and install**

version: "3"

services:

karakeep:

image: ghcr.io/karakeep-app/karakeep:release

ports:

- "3000:3000"

environment:

- NEXTAUTH_SECRET=changeme

- NEXTAUTH_URL=http://localhost:3000

- DATA_DIR=/data

- OPENAI_API_KEY=$OPENAI_API_KEY

volumes:

- karakeep-data:/data

chrome:

image: gcr.io/zenika-hub/alpine-chrome:123

command: --no-sandbox --disable-gpu --remote-debugging-address=0.0.0.0 --remote-debugging-port=9222

meilisearch:

image: getmeili/meilisearch:v1.13.3

environment:

- MEILI_NO_ANALYTICS=true

- MEILI_MASTER_KEY=changeme

volumes:

karakeep-data:

It runs as three containers — the app, a headless Chrome (for body extraction), and Meilisearch (for search). Fits on a small VPS.

**Why Pocket refugees love it**

OPML and CSV imports are solid, so you can move Pocket data straight in. AI tagging and summaries work as long as you bring an LLM API key, so a pile of bookmarks turns into an organized knowledge stash automatically. And since the code is all there, even if the company dies your data lives on.

**Weaknesses**

Installation is not hard but is still a barrier for users unused to self-hosting. The official managed SaaS (in beta as of writing) will smooth that out as it stabilizes. AI features cost the user money via the LLM API.

14. Omnivore (RIP, October 2024) — a short shining run

Omnivore launched in spring 2023 as an open source (AGPL) read-later app. iOS, Android, web, newsletter inbox, automatic body extraction, highlights, Logseq and Obsidian sync — it was the most serious open source candidate to replace Pocket.

Growth was very fast. GitHub stars passed 10k in spring 2024 and self-hosting guides spread widely. The free SaaS that Omnivore ran was costly to host.

Then in October 2024 the Omnivore core team announced they were joining ElevenLabs and the SaaS would shut down. Users had to export and migrate, mostly to Readwise Reader, Wallabag, and Karakeep.

**The lesson Omnivore left**

Even open source SaaS can disappear because of a company decision. As long as the code and data export are well defined, users have a path out. Omnivores shutdown was relatively clean — about two months of notice, OPML/JSON export, and self-hosting guides. It will be remembered as a well-shut-down case.

Another lesson is the economics of "open source SaaS" — a free service with many users and heavy infrastructure cannot persist without monetization. To avoid a similar fate, successors like Karakeep need to design SaaS monetization or sponsorship from the start.

15. Korea / Japan — the history of Daum RSS Reader and livedoor Reader

**Korea — the short golden age of Daum RSS Reader**

Around 2007 to 2008, Daum operated "Daum RSS Reader," a web-based RSS service. Korean encoding worked well and it integrated deeply with Korean blogs and press feeds. Hangame, Naver Blog RSS, all of it landed cleanly, and the mobile pages were fast.

But as the mobile era began and traffic dropped, the service was quietly shut down in the early 2010s. The exact date is fuzzy in the record but is estimated around 2013 to 2014. Korean RSS users then moved to Google Reader (which itself shut down in July 2013) and Feedly. No Korean-built RSS reader of significance emerged in the mobile era.

Two pivotal turning points for RSS culture in Korea: first, Daum, Naver, and Tistory grew their in-platform subscription mechanisms (blog neighbors, cafes), reducing the felt need for RSS. Second, in the late 2010s, the algorithmic feeds of Kakao News and Naver News absorbed mainstream information consumption. RSS shrank into the tool of developers, journalists, and researchers.

What is interesting is that RSS has been reappearing in Korean developer circles in the 2020s. Korean IT outlets like SlowNews, EO, Techily, and Yozm IT serve normal RSS feeds, and tools like Outstanding and rsshub help generate RSS for Korean sites that do not provide it. RSS did not die in Korea either — it stayed alive, small.

**Japan — livedoor Reader (Live Dwango Reader)**

In Japan, livedoor Reader had a long golden age. Launched by livedoor in 2006 as a web RSS reader, it was beloved for its keyboard-shortcut-driven fast UI. It was nicknamed "ldr" and was effectively the standard among Japanese IT folks for a long stretch.

In 2014, as livedoor passed from NHN to LINE and then to Dwango, the name changed to Live Dwango Reader. It kept running until August 31 2017 when it shut down. After the announcement, Japanese internet exploded with tributes, and clones like Fastladder appeared, but none matched the originals feel.

In Japan today, Inoreader is the most popular. Its UI is well-translated into Japanese and its keyboard shortcuts feel familiar to former ldr users. Feedly and Feedbin are used too, but Inoreader is effectively the standard. Reeder remains popular among Apple users.

**Common ground**

In both countries, the local RSS reader disappeared and people now depend on global services. Self-hosting culture leans slightly more active in Japan — there are richer Japanese-language guides for FreshRSS and Miniflux. Korea tends more toward SaaS (Inoreader, Feedly) or Apple ecosystem tools (Reeder, NetNewsWire).

16. Who should pick what — Apple loyalist / self-hoster / read-and-listen integrator / truly free

The conclusion. Four user types, four answers.

**Type 1 · Apple ecosystem loyalist**

- **Reeder 5** (one-time purchase) plus **Feedbin** (USD 5/month) or Inoreader free/Pro.

- If you like the new design, **Reeder (25)** plus Feedbin is also great.

- Want truly free? **NetNewsWire** plus iCloud sync.

- Want a separate read-later? Add **Readwise Reader** or **Matter**.

**Type 2 · Self-hoster**

- Lightness first → **Miniflux** (Go, single binary).

- Feature richness first → **FreshRSS** (PHP, extensions).

- Veteran with a settled workflow → **Tiny Tiny RSS**.

- Both SaaS and self-host options → **NewsBlur**.

- Use external clients (Reeder, NetNewsWire, Fluent Reader) on mobile via the GReader API.

- For read-later: **Karakeep** or **Wallabag**.

**Type 3 · Read-and-listen integrator**

- **Readwise Reader** (roughly USD 10/month) — RSS, PDF, EPUB, YouTube, newsletters, TTS, AI summaries, Obsidian and Roam sync in one app.

- **Matter** (roughly USD 8/month) — mobile first, excellent TTS, great for casual reading.

- Both offer free trials, so spend a month on each and decide.

**Type 4 · Truly free**

- **NetNewsWire** (Apple) plus iCloud sync = completely free.

- On other OSes, **Feedly free** (up to 100 sources) or **Inoreader free** (up to 150 sources).

- If you have the resources to self-host, run **Miniflux** or **FreshRSS** = completely free plus data control.

- Read-later: **Wallabag** self-hosted or **Instapaper free tier**.

**Pro user (journalist, researcher, security)**

- **Inoreader Pro** (USD 10/month) plus Reeder 5 or the new Reeder.

- All of keyword monitoring, newsletter receiving, rule-based automation, and team sharing in one place.

- For security intelligence, evaluate **Feedly Enterprise** with Leo AI.

**Final recommendation: manage your own OPML file**

Whatever service you use, regularly export an OPML file and keep it on your own disk. The greatest strength of RSS is that one OPML file moves every subscription to another service. We do not know which service will follow Pocket out the door. You must be able to carry your data with you.

RSS did not die. It simply became "the tool for people who want to control their own information diet," not "everyones tool." That group is growing again thanks to algorithm fatigue. Spring 2026 is RSS second spring. This time every tool is more diverse and more solid.

References

- Reeder 5 (Reinvented Software) — https://reeder.app/classic

- Reeder (25 model) — https://reeder.app/

- NetNewsWire — https://netnewswire.com/

- NetNewsWire GitHub — https://github.com/Ranchero-Software/NetNewsWire

- Inoreader — https://www.inoreader.com/

- Feedbin — https://feedbin.com/

- Feedly — https://feedly.com/

- Feedly Leo AI — https://feedly.com/i/landing/leo

- Miniflux — https://miniflux.app/

- Miniflux GitHub — https://github.com/miniflux/v2

- FreshRSS — https://freshrss.org/

- FreshRSS GitHub — https://github.com/FreshRSS/FreshRSS

- Tiny Tiny RSS — https://tt-rss.org/

- NewsBlur — https://newsblur.com/

- Pocket sunset notice (Mozilla) — https://support.mozilla.org/en-US/kb/future-of-pocket

- Instapaper — https://www.instapaper.com/

- Matter — https://hq.getmatter.com/

- Readwise Reader — https://readwise.io/read

- Karakeep — https://karakeep.app/

- Karakeep GitHub — https://github.com/karakeep-app/karakeep

- Omnivore shutdown announcement — https://blog.omnivore.app/p/details-on-omnivore-shutting-down

- Wallabag — https://wallabag.org/

- The Old Reader — https://theoldreader.com/

- BazQux Reader — https://bazqux.com/

- livedoor Reader shutdown (Wikipedia) — https://ja.wikipedia.org/wiki/Live_Dwango_Reader

- Google Reader shutdown (2013, Wikipedia) — https://en.wikipedia.org/wiki/Google_Reader

- SlowNews — https://slownews.kr/

- RSS Specification 2.0 — https://www.rssboard.org/rss-specification

- OPML 2.0 Spec — http://opml.org/spec2.opml

- rsshub — https://docs.rsshub.app/