forked from mirrors/fediprofile
Evaluate and add Spotify for Creators podcast RSS setup #38
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Provide service-specific setup and presentation for podcasts with a publicly enabled RSS feed from Spotify for Creators.
First decision
Verify whether a public show URL can reliably discover its public RSS feed. The official documentation describes obtaining the feed in creator settings, so automatic show-to-feed resolution remains unverified. If reliable public discovery is unavailable, support directly entered public RSS URLs and document that limitation.
Acceptance
Scope support to public podcast RSS feeds. A Spotify music artist/account URL is not a podcast feed, and Spotify availability alone does not establish RSS availability.
Respect the documented prerequisites: the first episode must have been published and external RSS distribution enabled. Handle absent feeds and shows hosted elsewhere without guessing a feed URL.
Present episode title, original link, show/author attribution, artwork, description, and available audio enclosure metadata. Reuse normal external-media handling rather than mirroring audio files.
Use the existing single add-account/link field and subscription-versus-link confirmation. Show the source name and original URL; public feed access must not imply account ownership.
Reuse the source ingestion/publication pipeline and service setup adapter introduced by #30. Preserve the provider in setup results rather than hard-coding YouTube. Use protected external fetches, rate limiting, the configured feed limit, and the configured polling schedule.
Add application-specific mocked unit tests to the interoperability suite for resolution, invalid/ambiguous inputs, imports, stable IDs, edits/deduplication, attribution, and rendered/federated links. Keep real-service checks in manual integration. Follow the repository's red/green process.
Keep the compatibility matrix, runtime classifications, and interoperability tests synchronized; document actual limitations.
Depends on #27 and #30. Official feed availability and enablement: https://support.spotify.com/us/creators/article/finding-and-enabling-your-rss-feed/