Improve Podcasting 2.0 coverage

Feature request
1

App version: 3.0.2

Problem you may be having, or feature you want:
A lot of other apps score higher on Apps | Podcastindex.org

Phase 1 (Closed on 11/15/20)

podcast:locked
podcast:transcript
podcast:funding
podcast:chapters
podcast:soundbite

Phase 2 (Closed on 1/31/21)

podcast:person
podcast:location
podcast:season
podcast:episode

Phase 3 (Closed on 6/1/21)

podcast:trailer
podcast:license
podcast:alternateEnclosure
podcast:source
podcast:integrity
podcast:guid

Phase 4 (Closed on 12/1/2021)

podcast:medium
podcast:images
podcast:liveItem

Phase 5 (Closed as of 7/15/2022)

podcast:socialInteract
podcast:block

Phase 6 (Closed as of 6/1/2023)

podcast:txt
podcast:remoteItem
podcast:podroll
podcast:updateFrequency
podcast:podping
podcast:valueTimeSplit

Suggested solution:
Implement more features of the Podcasting 2.0 standard as describe in GitHub - Podcastindex-org/podcast-namespace: A wholistic rss namespace for podcasting

Screenshots / Drawings / Technical details:
The Podcasting 2.0 standard offers a variety of features like better chapter marks, transcripts with timestamps, Alternate Enclousers,linking guests and various other improvements.
You don’t need to include the Cryptocurrency part of the Value 4 Value idea, but some of these are really useful

1 Like
2

The following ones are irrelevant to AntennaPod: locked, guid, medium, images, block, txt, remoteItem, podping.

3

podcast: transcript was just merged and will be available in 3.5 x release

6 Likes
4

Isnt a unique id for a podcast and a podcast episode helpful with deduplication and updates to hosting and episodes that were broken?

5

There already is a unique id that people don’t use properly. Yet another one will probably not make things better.

6

This is not irrelevant. It would be cool to display them as regular episodes.

This might not be irrelevant per se. We could leverage it to have a different background in the podcast header and/or Chromecast backdrop.

As far as I’m aware, there’s no guid identifier at channel level – only at item level (?) This tag in the podcast namespace is at channel level.

@ghast we have discussed it in the context of podcast synchronisation.

This is not irrelevant per se. We could change the default sorting for audiobook podcasts, for example. I think there’s a feature request in our repo linked/related to this.

Indeed, block, lock, txt & podping are irrelevant for us. @ghast would you mind updating your initial post? Also, given that the PC2.0 GitHub overview page (to which you link) sucks, it’d be great if you could make the individual tags in your list link to the individual spec sections. Then we can tap on your list items and see directly what it’s all about. (I can help with that if needed.)

1 Like