https://podcast-index-browser.vercel.app/certified now checks CORS see attached screenshots. All using https://www.npmjs.com/package/podcast-partytime
Still plan to do more testing of the parser.
@RyanHirsch I just tried the RSS feed I linked here for kicks and giggles... getting a 500 response that says "Boom" :)
@agates should be fixed, you don't have any categories on that feed, and the code didn't handle that very well
@RyanHirsch Very cool. Something else that would be helpful is verifying that images are served over HTTPS.
@RyanHirsch Another thing that would be helpful is verifying the image can be hotlinked to through the browser. For example
has an image link of
which doesn't allow hotlinking as shown in the screen shot below
@RyanHirsch My feed doesn't get a tick for Value, however I do have it in.
@brianoflondon I don't have phase 3 working yet, I should remove it from the display :D
I prioritized the CORS stuff. I'll have it working soon*
@RyanHirsch it doesn’t work at all when I put my feed in https://feeds.podcastmirror.com/dudesanddadspodcast
@RyanHirsch Does a tick in a slightly lighter colour really mean a "cross" - that it isn't in the feed? What does the CORS stuff mean - how do I fix that (if I do?)
@jamescridland the light color means the server attempted to verify that aspect the feed but it didn’t “pass”.
In your screen shot CORS was attempted but ultimately failed. This is generally a responsibility of the hosting provider and their configuration.
Failure means the endpoints are locked down so that other websites cannot directly access that content. Any web based podcast player or tool will have to go through a proxy to access the resource.
We probably also need an article to explain what CORS is, and what it means if you fix it.
In this case, yes James you would have to fix it yourself.
What it means eg. is if you want to allow a web app to read your RSS feed (or the audio/transcript) directly, and not through a proxy.
In almost all cases for podcasts, you do want that.
When the webserver returns your rss feed, the transcript files, chapter files and audio files.
For example I use PHP and have the following lines:
@martin @RyanHirsch @jamescridland
I'd like to point out that cors for the enclosure is not imo critical. Web players can still play the audio. Control the playback speed, volume etc.
Cors would allow more advanced features like waveform display or audio processing like compression.
The more important (in pc20 point of view) is that you have cors working on chapters and transcripts because they are totally useless without cors or proxy.
Just my 2c 🙂.
@jamescridland @ville @RyanHirsch
@RyanHirsch "the light color means the server attempted to verify that aspect the feed but it didn’t “pass”."
Please consider a clear cross rather than a tick; and to use accessible colours that are visible to those on a bad monitor or with degraded sight.
@jamescridland @RyanHirsch @martin I agree that a clear CORS write up is a good idea. It would be nice to post up Adam’s Podcasting 2.0 document and then section link directly from the checker to each relevant explanation. CORS is a big topic, with some security caveats to consider if someone is hosting their podcast files on their main host name.
Intended for all stake holders of podcasting who are interested in improving the eco system