@silas afaik podpings are merely “rss feed updated” signals. The rss feed should (but isn’t guaranteed to) be updated before a Podping is broadcast. The RSS feed is still the source of truth and should be parsed to determine current live start or live ended status.

@mitch yes I thought about it since posting that. I haven't changed anything yet but I think I will have it try to reparse the feed like every minute or so maybe 2 or 3 times. See if any live item changes then. There's too many rss feeds with several live items to make assuming which one is meant to go offline hard.
I also need to put something in for when they don't do anything at all. Sometimes people don't change or even send a podping out either.

@silas we've been using @js's livewire podping listener for a few years now, and it seems to be quite reliable for detecting podpings.

Re: "reparse the feed every minute", I would suggest the responsibility is on the podcaster (usually their RSS feed hosting company) to make sure their RSS update process is aligned with the Podping process.

We've run into issues with requesting cached feeds in the past, but that is something that should also be handled by the RSS host.

podverse/packages/mq/src/functions/mq/rss/runLiveItemListener.ts at develop · podverse/podverse

Podverse monorepo for all infrastructure, modules, applications, and deployments - podverse/packages/mq/src/functions/mq/rss/runLiveItemListener.ts at develop · podverse/podverse

GitHub (github.com)