> Ideal would be an URI like podcast:// No, that would be far from ideal, for the same reason that the feed[1] URI scheme was flawed (cooked up by very confuse

> Ideal would be an URI like podcast:// No, that would be far from ideal, for the same reason that the feed[1] URI scheme was flawed (cooked up by very confused people) from the beginning. And among other things, a podcast:// URI would now mean I can't open the thing in my browser unless my browser vendor adds support and I download the new version. The file is served over HTTP(S). Just use the http or https URI. Podcast players need to do their part[2] in dealing with them. 1. <https://en.wikipedia.org/wiki/Feed_URI_scheme https://en.wikipedia.org/wiki/Feed_URI_scheme> 2. <https://news.ycombinator.com/item?id=37691360 https://news.ycombinator.com/item?id=37691360>