Relative Podcasting2.0 chapter urls

1

Hello,
I am developing a library/tool which (among other things) generates an rss feed for a podcast.
The primary client for the rss feed generated by this library is AntennaPod, as that’s what I use.
I have a few questions about Podcasting2.0 chapters:

  • Does AntennaPod support relative chapter urls? I tried urls like:
    <podcast:chapters url="yJ3ZvJSDE6aZ-chapters/chapters-V6sksZjGnQwM.json" type="application/json+chapters"/>
    but it the chapters just kept loading forever.
  • If AntennaPod supports relative chapter urls, what is the syntax?

Note: I made sure that my xml element has the appropriate xmlns:podcast="https://podcastindex.org/namespace/1.0" and version="2.0"

I am using the nodejs “podcast” library (github: maxnowack/node-podcast) under the hood in my tool (extra logic + customizations on top)

I am interested in this, as previously I used the simple psc-style podlove chapters, and those can’t seem to be force-refetched from antennapod (the refresh button is invisible from my testing), which makes testing chapter support quite difficult.

Thanks!

2

Relative urls in rss feeds are super error prone. Don’t do that! What are they relative to? The original url of the podcast? The final redirect? The podcast website mentioned in the rss? There is no definite answer and you will run into trouble. Just make them absolute :slight_smile:

3

I made them relative to the sub-folder that the feed is in, e.g.

https://example.com/some/subfolder/feed-1.xml

has chapters at:

https://example.com/some/subfolder/feed-1-chapters/ep1.json

using the relative url in the xml:

feed-1-chapters/ep1.json

If this is not viable, i’ll make them absolute. i’ll have to make some changes, because right now, the feed generator doesen’t know or care what the final deployment url will be, that’s why i wanted to use relative urls, but the change is not very difficult, so i’ll just use absolute urls, as you suggested. thx for the answer!

1 Like