Mention me in your support request!
Ah 477k of the 561k were just HEAD requests. Thats good!
One RSS feed was requested 84 times....in 30 minutes...from just ONE of their user agents.
FWIW, I don't think it's particularly useful to add anything to the tag spec to indicate finality or updates — that's exactly the kind of detail, like HTTP 304 handling, that the real world would get wrong all the time and force apps like mine to partly ignore and poll after a while anyway.
I think I'll go with my initial instinct: fetch at download time, and again at play time, proxied through my servers to reduce trackability.
For the first month ever, Spotify has passed Apple Podcasts for the most Buzzsprout downloads 😬 https://www.buzzsprout.com/global_stats
There! I had to get it off my chest!
I think our focus should be 100% on improving the podcasting experience in an open-standard way that allows every player to innovate faster and better than any one company could do on their own. This is our best bet at avoiding one company emerging as the monopoly of podcasting.
I was struck by how similar this is to what we are doing with Podcasting 2.0 and the RSS namespace. Android allowed all of Apple's competitors to keep up with Apple's innovations and level the playing field.
Podbean is still under attack. We’re all sharing notes to help each other. Podcasting community FTW!
Buzzsprout now supports images in chapters: Here is an example: https://feeds.buzzsprout.com/264670/7752958/chapters.json.
Intended for all stake holders of podcasting who are interested in improving the eco system