klafbang/fediprofile
Watch
1
0
Fork
You've already forked fediprofile
 0
forked from mirrors/fediprofile
Code Issues 8 Pull requests Packages 2 Activity Actions

Evaluate and add SoundCloud podcast RSS source setup #37

New issue
Open
opened 2026-09-30 04:24:08 +00:00 by Michael Westergaard · 0 comments
Michael Westergaard commented 2026-09-30 04:24:08 +00:00
Owner

Goal

Provide SoundCloud-specific setup and presentation for tracks that their creator has included in a public podcast RSS feed.

First decision

Verify whether a public SoundCloud profile exposes a reliable RSS discovery method. Do not invent a profile-to-feed URL mapping. If it cannot be resolved reliably, support directly entered public SoundCloud podcast RSS URLs with service-specific presentation and explain the profile-URL limitation.

Acceptance

  • Support only the account's available podcast feed and tracks explicitly included in it. Do not claim that all public SoundCloud uploads are imported; SoundCloud documents one RSS feed per account.

  • Validate feed/profile association where public metadata permits it. Handle an absent or unconfigured feed without selecting another account's feed.

  • Present podcast/track title, original page link, artwork, description, source attribution, 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 setup and opt-in track inclusion: https://help.soundcloud.com/hc/en-us/articles/31378915079963-Set-Up-Your-Podcast-s-RSS-Feed

## Goal Provide SoundCloud-specific setup and presentation for tracks that their creator has included in a public podcast RSS feed. ## First decision Verify whether a public SoundCloud profile exposes a reliable RSS discovery method. Do not invent a profile-to-feed URL mapping. If it cannot be resolved reliably, support directly entered public SoundCloud podcast RSS URLs with service-specific presentation and explain the profile-URL limitation. ## Acceptance - Support only the account's available podcast feed and tracks explicitly included in it. Do not claim that all public SoundCloud uploads are imported; SoundCloud documents one RSS feed per account. - Validate feed/profile association where public metadata permits it. Handle an absent or unconfigured feed without selecting another account's feed. - Present podcast/track title, original page link, artwork, description, source attribution, 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 setup and opt-in track inclusion: https://help.soundcloud.com/hc/en-us/articles/31378915079963-Set-Up-Your-Podcast-s-RSS-Feed
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
michael
main
features/single-user-instance
0.9.16
0.9.15
0.9.14
0.9.13
0.9.12
0.9.11
0.9.10
0.9.9
0.9.8
0.9.7
0.9.6
0.9.5
0.9.4
0.9.3
0.9.2
0.9.1
0.9.0
0.0.3
0.0.2
0.0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
klafbang/fediprofile#37
No description provided.