@dave@podcastindex.social Not really all that different from Kubernetes or Heroku auto scaling....just that it can turn them all off...and not turn any of them on sometimes, haha!
Remote
Nathan
@nathan@podcastindex.social
mastodon 4.7.3Developer, podcast enthusiast, worked on developing multi-lingual podcasting tools. Glad to see new life breathed into RSS. Go Podcasting!!! @npruzaniec on GitHub
4 Followers
2 Following
10 Posts
Joined November 19, 2020
@dave@podcastindex.social Agreed, it's kind of outside the namespace but I think solving everything through namespace might not always be best. Thankful for your work on this!
Replying to
@dave@podcastindex.social Maybe just having *.rss?offset=12 or *.rss?pg=2 still allows the feed's policy of how many episodes per feed file to be maintained.
Replying to
Alternately an updated="" attribute for a timestamp could be used on the XML element.
I am managing a podcast feed hosted with WP + PowerPress. Sometimes it seems the Podcast Index doesn't pick up new episodes randomly and when that happens it also seems Spotify doesn't update the feed either so I'm wondering if something is wrong with the feed. Any thoughts/suggestions/ideas to troubleshoot?
https://podcastindex.org/podcast/6981463
https://larrysrrr.com/feed/podcast/
@dave@podcastindex.social It totally is. I'm building some data ingest and transformation tools on Lambda now and I only feel ok about it because none of it is particularly uptime sensitive. AWS has so many strange and ephemeral limitations and things that can go wrong -- like too many tasks running at once in this region, yours got cancelled. It's all becoming more and more intangible.
Replying to
@adam@podcastindex.social Yeah, that definitely works, but this would be a way to let a reader or aggregator know when a particular file is updated without having to request the file.