Hi, sorry I missed this thread. Yes, the direction of web is pretty hostile to what we're trying to do. If you're an SSL site, non-SSL podcast streams will play on fewer and fewer browsers. Paired with this, CORS issues are spreading to more web API's over time.
If hosting costs aren't an issue, the obvious way to fix this is to proxy through your own web server. The real problem is a lack of a web API security model.
@dave Do you have a pointer to a spec for podcast:soundbite? I need to look at that. Thanks!
@theDanielJLewis Don't you think it would be so much better in XML? 😋
Ok, podbrowser.org's showing chapter labels (and images, if set). I give the image a small screen space, but you can click on it to expand it into its own tab.
@martin you are doing God's work to give podcasters tools to add this data to their episodes!
@dave You mean corporate accomodation by github? Tons of articles, for instance:
@drunkplato That's not the tricky and insidious part of Github. It's that you depend on PR's, and issue tracking, and team discussion, and .... None of it open source, or easily rehosted.
On the subject of encoding payment/support:
If you two can link up in real time, you can dump/restore from a stream (I suggest mbuffer) and avoid the intermediate file storage:
Author of the old OS VSTa, lots of networking, more recently bunches of web stuff.
My open source is at http://sources.vsta.org/
Intended for all stake holders of podcasting who are interested in improving the eco system