Add Substack-specific RSS source setup and presentation #34

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

Goal

Let a user enter a Substack publication URL and subscribe without finding its RSS feed.

Acceptance

  • Resolve a publication's name.substack.com URL to its documented /feed URL. Evaluate custom-domain publications through verified discovery rather than assuming every custom domain is Substack.

  • Distinguish publication URLs from personal profiles, individual posts, and other Substack pages. Reject ambiguous inputs rather than silently selecting a publication.

  • Present each available feed item with its title, original link, author/publication attribution, and available media metadata. Import only content exposed by the public feed; document its observed content limitations.

  • 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 format: https://support.substack.com/hc/en-us/articles/360038239391-Is-there-an-RSS-feed-for-my-publication

## Goal Let a user enter a Substack publication URL and subscribe without finding its RSS feed. ## Acceptance - Resolve a publication's `name.substack.com` URL to its documented `/feed` URL. Evaluate custom-domain publications through verified discovery rather than assuming every custom domain is Substack. - Distinguish publication URLs from personal profiles, individual posts, and other Substack pages. Reject ambiguous inputs rather than silently selecting a publication. - Present each available feed item with its title, original link, author/publication attribution, and available media metadata. Import only content exposed by the public feed; document its observed content limitations. - 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 format: https://support.substack.com/hc/en-us/articles/360038239391-Is-there-an-RSS-feed-for-my-publication
Sign in to join this conversation.
No labels
No milestone
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#34
No description provided.