-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Podcast chapters #302
Comments
It was moved to an external file to prevent the feed becoming too big, or
cluttered, for performance and bandwith concerns.
Le lun. 11 oct. 2021, 19:16, Klaas Foppen ***@***.***> a
écrit :
… I am implementing chapters in my app but I am curious what has been the
reasoning behind having chapters behind another API call? Why not make the
chapters part of the actual feed?
<podcast:chapters version="2.0">
<podcast:chapter start="0" title="Welcome" />
<podcast:chapters start="3:07" title="Star episode" />
</podcast:chapters>
(Simple example)
I understand the proposal is already gone trough but was there a specific
reason to have chapters in JSON?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#302>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADST7NW4ZXI3LIEQRXDNR3UGMLXLANCNFSM5FYWMRTA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Plus, the chapters are simply one part of additional episode data. So it's really not a "chapters file" but an "episode metadata" file that can contain other data. |
Yes, we were discussing in #184 about moving all "episode metadata" to a file. Podcast clients would download this file when downloading episode or accessing the episode infos |
I'll add that we were told by more than one large host that adding the chapters to the feed itself would prohibit them from implementing. So, it was just a no-go out of the gate. |
Yeah adding the chapters to the feed is a lot of clutter. Every app doesn't need the chapters for every episode. It makes sense that it is an additional HTTP call. The proper use of ETags and HTTP 304s should eliminate the need for a hash as well. |
Well, using a hash will eliminate the need of a request at all IMHO 😁 But that's a debate to have in the #184 issue |
@klaaz0r If you want to put your chapters directly into the RSS feed you can use https://podlove.org/simple-chapters/ which was established in 2012 and is already supported by Podcast Addict, Antenna Pod, Podcat, etc. So in my opinion this issue can be closed. |
I am implementing chapters in my app but I am curious what has been the reasoning behind having chapters behind another API call? Why not make the chapters part of the actual feed?
(Simple example)
I understand the proposal is already gone trough but was there a specific reason to have chapters in JSON?
The text was updated successfully, but these errors were encountered: