You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some podcasts (like PC2.0) have a placeholder chapter in case no chapters are available (yet), even though a chapter file is already linked in the feed. This may happen, for example, if a podcast(er) relies on the community to provide chapters, and they may come a few days after the episode. However, such placeholder chapter may be confusing for the end-users, who might think (as I did) that their app doesn't have cached the latest chapter information, or that there was an error parsing the chapters as there is only one and usually there are more.
If the chapter file is absent or empty, even when linked from the feed, this must be expected and handled gracefully by apps. In this case, apps may display no chapter user interface or display information that chapters are not available yet.
If the chapter file contains no chapters but human-readable info (in a format that should be defined, I suppose), apps may display this text (or ignore it and stick to the scenario above). (E.g. in AntennaPod there is a chapters button, which in this situation could have an info icon instead of previous/next icons; the usual modal could display the text instead of the chapters list.) This possibility can be leveraged by podcasters to advertise the fact that they do have chapters (even though they're not available yet) and explain when chapters are to be expected and why they're not available yet.
I think this is good and you should consider the scenario when the episode metadata file contains other data but not chapters. (It's a file for more than only chapters, so it's not only a chapters file.)
As discussed in this thread: https://mastodon.social/@keunes/108957034896398550
Some podcasts (like PC2.0) have a placeholder chapter in case no chapters are available (yet), even though a chapter file is already linked in the feed. This may happen, for example, if a podcast(er) relies on the community to provide chapters, and they may come a few days after the episode. However, such placeholder chapter may be confusing for the end-users, who might think (as I did) that their app doesn't have cached the latest chapter information, or that there was an error parsing the chapters as there is only one and usually there are more.
Therefore I suggest we update the podcast:chapters specs such that:
Cc: @daveajones
The text was updated successfully, but these errors were encountered: