Domain: Episodes

[keunes]

From meeting notes:

• The database often overflows due to a large dataset being stored. All actions are stored and never cleaned up, and all episode actions can only be stored once. E.g:
  • If you listen to an episode once and then listen again, an action such as “new” is only sent once.
  • Sending the exact same play position once cannot be stored twice.

Existing gPodder API specs: Episode Actions API to upload (register) and get download, play, delete, new (really more 'reset') actions.

[keunes]

https://help.apple.com/itc/podcasts_connect/#/itcb54353390

GUID
The episode’s globally unique identifier (GUID) If you uploaded subscriber audio in Apple Podcasts Connect and need to link it to an episode in your RSS feed, you can use the Apple Podcasts Episode ID in the GUID tag. Learn more about how to set up your show for a subscription.

It is very important that each episode have a unique GUID and that it never changes, even if an episode’s metadata, like title or enclosure URL, do change.

Globally unique identifiers (GUID) are case-sensitive strings. If a GUID is not provided, an episode’s enclosure URL will be used instead. If a GUID is not provided, make sure that an episode’s enclosure URL is unique and never changes.

Failing to comply with these guidelines may result in duplicate episodes being shown to listeners, inaccurate data in Analytics, and can cause issues with your podcasts’s listing and chart placement in Apple Podcasts.

See also https://code.castopod.org/adaures/castopod/-/issues/284

[keunes]

Related: #2 (duplication)