I've extracted partytime from the aggregator and have a basic certification check. It is only looking at phase 1 because it's a direct port of what @dave put up 3 months ago.
I haven't published it as a separate package yet. I also need to prettify the response.
@dave plan on it. I didn’t do much but copy and paste your code and clean some stuff up my linter got angry with.
What determines a feed's CORS support? I understand CORS, but what endpoint needs to be CORS enabled, the actual feed? ie PC 2.0 is NOT compliant based on this screenshot -
@dave @RyanHirsch If we are differentiating then I guess I am fine with it just being a recommendation :)
It does make life a lot easier for web apps though, and it also makes it possible to make things like silence skip, waveform visualizations etc. from the web, which is not possible in a browser without CORS on the audio.
@martin @RyanHirsch The next feed dump will have a field containing the most recent episode's enclosure url for each feed. I'd love for someone to take that and see which major hosts do not support CORS for the XML feed itself and the audio file.
For the PC20 feed, we can talk to VoidZero about changing that.
Intended for all stake holders of podcasting who are interested in improving the eco system