Flame
Self-hosted dashboard that finished its feature arc and stopped shipping in 2023.
A side-by-side editorial comparison of CommaFeed and NetNewsWire — release velocity, themes, recent moves, and the top alternatives to consider.
A self-hosted RSS reader that now spends most of its release notes on security.
CommaFeed is a self-hosted Google Reader replacement that has spent the 6.x-to-7.x stretch rebuilding its trust boundaries rather than its feature list. SSRF protection has been tightened in four consecutive releases, feed parsing now strips javascript: URLs before they reach the database, and OPML imports are filtered against import-time abuse. The 7.x line pairs that with client interop: Fever API, ReadKit compatibility, and now the Google Reader API.
NetNewsWire rebuilt Feedly sync to stop getting its own users rate-limited.
The centerpiece of this window is a Feedly sync overhaul, shipped in parallel to iOS and Mac: syncing now backs off when Feedly reports rate limiting, fetches only what changed, caps downloads per refresh, and directly refreshes a few feeds each pass to backfill articles Feedly's aggregate stream omits. The mark-as-read backlog that could grow without bound and re-send the same statuses was fixed, and articles now use Feedly's reported publish dates instead of arriving all stamped today. Around it sits a dense stream of small point builds on both platforms, including a move to the current Sparkle framework and a filter-button style that was introduced and reverted within two days.
CommaFeed is a self-hosted Google Reader replacement that has spent the 6.x-to-7.x stretch rebuilding its trust boundaries rather than its feature list. SSRF protection has been tightened in four consecutive releases, feed parsing now strips javascript: URLs before they reach the database, and OPML imports are filtered against import-time abuse. The 7.x line pairs that with client interop: Fever API, ReadKit compatibility, and now the Google Reader API.
The project is positioning itself as a sync backend other people's apps talk to, not just a web reader. Each release adds another protocol or client fix while hardening the assumption that an instance may be publicly exposed with untrusted users on it. The 7.0.0 swap from JEXL to sandboxed CEL and the 7.3.0 flip of blockLocalAddresses to a secure default both trade self-hoster convenience for a safer out-of-the-box posture.
Expect continued client-protocol coverage and further SSRF narrowing; the recurring pattern in these entries is that every new fetch path gets a follow-up hardening release.
The centerpiece of this window is a Feedly sync overhaul, shipped in parallel to iOS and Mac: syncing now backs off when Feedly reports rate limiting, fetches only what changed, caps downloads per refresh, and directly refreshes a few feeds each pass to backfill articles Feedly's aggregate stream omits. The mark-as-read backlog that could grow without bound and re-send the same statuses was fixed, and articles now use Feedly's reported publish dates instead of arriving all stamped today. Around it sits a dense stream of small point builds on both platforms, including a move to the current Sparkle framework and a filter-button style that was introduced and reverted within two days.
This is a maintenance-phase release train, and the work is concentrated where the app depends on someone else's service. Making sync well-behaved enough not to trigger bans is infrastructure debt being paid down rather than new capability, and the same is true of the Sparkle switch, which pre-empts breakage on macOS 27 betas. The parallel iOS and Mac numbering means most substantive changes land twice, so the feed reads busier than the change set actually is.
Expect 7.1.3 to converge to a shipping release on both platforms with no new capability, given the last several builds are fixes and one reverted style change. Further hardening of third-party account syncing is the most likely next area, since Feedly consumed this cycle.
Other Collab products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either CommaFeed or NetNewsWire.
Self-hosted dashboard that finished its feature arc and stopped shipping in 2023.
SiYuan's v3.8.0 train restates one AI feature set across seven consecutive builds.
Jellyfin renumbers to 12.0 and spends the whole cycle paying down its backend rewrite.
Teable is spending its release budget making bring-your-own-database failures survivable.
Happeo's feed is a buyer-education funnel, not a changelog — no shipped work is visible.
Staffbase's public feed is employer branding, not product — the release signal isn't here.
See all CommaFeed alternatives → · See all NetNewsWire alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CommaFeed and NetNewsWire are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. CommaFeed and NetNewsWire are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
Top CommaFeed alternatives in Collab are ranked by recent ship velocity. Browse the "CommaFeed alternatives" section above for the current picks, or visit /alternatives/commafeed for the full list with editorial commentary on each.
Top NetNewsWire alternatives in Collab are ranked by recent ship velocity. Browse the "NetNewsWire alternatives" section above for the current picks, or visit /alternatives/netnewswire for the full list with editorial commentary on each.