Podcasts often made available on lots of platforms and apps. That would mean the podcast owner would need to check all of those places regularly to respond to people - if they miss a platform they'd be accused of ignoring their audience by people who listen there. That's a lot of effort. Rather than doing that podcasters often have a website for their podcast that (sometimes) lets listeners engage with them, or they use social media with a Twitter or Insta account for the podcast.
Or, also because podcasts aren't standardized, if podcasts had a standard there would be a podcast standardization track, then there would probably end up being specified the possibility of adding comments to the payload and a way to specify endpoints for receiving comments. etc.
This would of course also open up for other things like perhaps including resources at a particular point in the podcast that the user could respond to - for example links to relevant demos of technique under discussion etc.
And probably a greater development of different podcast players.
This would of course also open up for other things like perhaps including resources at a particular point in the podcast that the user could respond to - for example links to relevant demos of technique under discussion etc.
Minus the “that the user could respond to” but isn’t that just show notes and/or chapters?
Those are already a thing as supported by, e.g., Overcast [1]. Overcast also has a function to share short clips, which I guess is similar to being able to link to specific points in a podcast. Podcasters don’t use the functionality available, though.
Podcasters don’t use the functionality available, though.
As a general rule content providers of any sort do not make use of functionality available in one content serving application, unless that application has near monopoly control of the market. Overcast evidently does not https://www.reddit.com/r/podcasts/comments/8ntp3x/podcast_ap... (unless stuff has changed drastically in last two years)
When it’s supported by the majority of clients though [1]…
MP3 chapter markers are supported by most podcast clients, including Apple Podcasts on iOS (provided you're on iOS 12), Overcast, Pocket Casts, Antennapod Castro, Player FM and more.
Almost all podcast apps are still RSS based. Podcasts are in some ways the last mainstream bastion of RSS (despite Apple at one point trying to kill their reliance on RSS, but giving up and going back to RSS).
The larger RSS ecosystem already had semi-related standards for comments support such as Pingback/Trackback/Webmentions. It should be possible to reuse/recycle some such existing standards to the podcast world, if there were interest from different player makers.
You don’t have to centralise podcasts to centralise comments, you could do something similar to disquss and use the ID/hash of the podcast episode then offer some iframe for various outlets to use (assuming they would want to use your service).
Even if no one uses your service you could just have a site where people go to comment.
Comments
Because podcasts aren't centralized..
Podcasts often made available on lots of platforms and apps. That would mean the podcast owner would need to check all of those places regularly to respond to people - if they miss a platform they'd be accused of ignoring their audience by people who listen there. That's a lot of effort. Rather than doing that podcasters often have a website for their podcast that (sometimes) lets listeners engage with them, or they use social media with a Twitter or Insta account for the podcast.
Or, also because podcasts aren't standardized, if podcasts had a standard there would be a podcast standardization track, then there would probably end up being specified the possibility of adding comments to the payload and a way to specify endpoints for receiving comments. etc.
This would of course also open up for other things like perhaps including resources at a particular point in the podcast that the user could respond to - for example links to relevant demos of technique under discussion etc.
And probably a greater development of different podcast players.
Minus the “that the user could respond to” but isn’t that just show notes and/or chapters?
Those are already a thing as supported by, e.g., Overcast [1]. Overcast also has a function to share short clips, which I guess is similar to being able to link to specific points in a podcast. Podcasters don’t use the functionality available, though.
1: https://imgur.com/a/X99bPqX
As a general rule content providers of any sort do not make use of functionality available in one content serving application, unless that application has near monopoly control of the market. Overcast evidently does not https://www.reddit.com/r/podcasts/comments/8ntp3x/podcast_ap... (unless stuff has changed drastically in last two years)
When it’s supported by the majority of clients though [1]…
1: https://chaptersapp.com/faq/
Thanks for the info!
Almost all podcast apps are still RSS based. Podcasts are in some ways the last mainstream bastion of RSS (despite Apple at one point trying to kill their reliance on RSS, but giving up and going back to RSS).
The larger RSS ecosystem already had semi-related standards for comments support such as Pingback/Trackback/Webmentions. It should be possible to reuse/recycle some such existing standards to the podcast world, if there were interest from different player makers.
You don’t have to centralise podcasts to centralise comments, you could do something similar to disquss and use the ID/hash of the podcast episode then offer some iframe for various outlets to use (assuming they would want to use your service).
Even if no one uses your service you could just have a site where people go to comment.
As long as there’s an RSS feed this is possible