Which source delivers, and which one has gone quiet?
Intake per RSS source, rhythm by weekday and hour, dominant topics. Plus the list of active feeds that delivered nothing in the period.
What you can do with it
- See for 7, 30 or 90 days how many stories came in and how many sources delivered.
- Find the active sources that delivered nothing in the period.
- Rank the strongest sources, with their weekend share and most frequent topics.
- Read on which weekdays and at which hours sources publish.
- Go through the busiest days and the latest scan runs with their most productive sources.
- See which topics dominate the intake, regardless of source.
The thinking behind it
A dead RSS source doesn't stand out. It throws no error; it simply stops delivering. Without a list that says so, nobody notices for weeks.
The rhythm isn't an end in itself: if you know when a source usually publishes, you know when an empty intake is normal and when it's an outage.
The analysis runs over tens of thousands of stories. So the server trims the result to what the page shows and recomputes at most every ten minutes.
A dead source throws no error. It simply stops delivering.
Improvements
Analysis is cached
The analysis is cached and no longer hits the database on every request.
A fraction of the data
The server trims topics and scan runs to what the page displays. The response used to be over two megabytes.
Consistent controls
Period switch, loading state, error message and tables now follow the design system used across the app.
Its own place under “Today”
The analysis belongs to the question the day starts with: is everything running that should be?
Give feedback or ask a question
Missing something, bothered by something, unsure about something? Write it down here — it goes straight to the people working on this feature.
Or write to us right here: