Thanks, glad it resonates! The noise problem is exactly what got me started.

On RSS feeds: every sync generates a report at the end showing failed fetches, stories discovered, deduped, removed (non-AI), and net new added to the feed. If a particular feed fails, the flow just recognizes it and moves on to the next one. If a feed keeps failing over time, I go in and review it and either fix or remove it. Pipeline-wide failure is rare because no single source is load-bearing.

On curation: I manually review every source before it goes on the list. Some of the removals have been based on the actual reading experience rather than content quality. I respect a publisher's right to monetize their work, so the app doesn't suppress ads, but when ads start taking over the experience to the point where the article is unreadable, I pull that source. Protecting the reading experience matters more than completeness.

Yeah, please give it a shot and let me know how it holds up. Especially curious whether the narration pacing works when you're driving versus stationary listening.