Flame
Self-hosted dashboard that finished its feature arc and stopped shipping in 2023.
A side-by-side editorial comparison of Jellyfin and NetNewsWire — release velocity, themes, recent moves, and the top alternatives to consider.
Jellyfin renumbers to 12.0 and spends the whole cycle paying down its backend rewrite.
Jellyfin is deep in a 12.0 release-candidate train — five RCs since late June — that exists almost entirely to stabilize the backend rewrite shipped in 10.11.0. The project also renumbered along the way: 10.11.x becomes 12.x, dropping a leading "10." that had made every release read as minor. The outgoing 10.11.x stable line is still getting fixes, but 10.11.11 is down to a single locking change.
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.
Jellyfin is deep in a 12.0 release-candidate train — five RCs since late June — that exists almost entirely to stabilize the backend rewrite shipped in 10.11.0. The project also renumbered along the way: 10.11.x becomes 12.x, dropping a leading "10." that had made every release read as minor. The outgoing 10.11.x stable line is still getting fixes, but 10.11.11 is down to a single locking change.
The RC rounds are getting narrower as the train converges. RC1 was a cumulative dump covering the move to .NET 10, removal of legacy API route middleware and deprecated API members, and an HLS transcode seeking refactor; RC5 is batched database lookups and a fix for image endpoints upscaling past the source resolution. The 10.11.x branch is now being maintained mainly as an upgrade floor — 12.0 refuses to install on anything older than 10.10.7 and runs a multi-minute migration on first boot.
With RC5 down to query batching and individual endpoint fixes, a 12.0 final looks near — likely one or two more RCs at most. The plugin story is the loose end: the RCs still tell testers to disable external plugins and reinstall from the unstable repository, and that has to resolve before a general 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 Jellyfin or NetNewsWire.
Self-hosted dashboard that finished its feature arc and stopped shipping in 2023.
A self-hosted RSS reader that now spends most of its release notes on security.
SiYuan's v3.8.0 train restates one AI feature set across seven consecutive builds.
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 Jellyfin 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. Jellyfin 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. Jellyfin 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 Jellyfin alternatives in Collab are ranked by recent ship velocity. Browse the "Jellyfin alternatives" section above for the current picks, or visit /alternatives/jellyfin 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.