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

Add WordPress-specific RSS and Atom source setup #35

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

Let a user enter a public WordPress site or author archive URL and subscribe to the appropriate posts feed.

Acceptance

  • Support the documented site feeds /feed/ and /feed/atom/, plus author archive feeds /author/name/feed/. Support WordPress.com sites and verified self-hosted WordPress sites.

  • Validate that the selected feed represents the requested site or author. Do not select comments, tag/category feeds, or an entire site's posts when the user entered an author archive.

  • Preserve ActivityPub account detection where the site also supports federation. Offer the normal feed subscription/link choice for RSS/Atom setup.

  • Handle private/disabled/unavailable feeds and excerpt-only feeds. Present original post links and author/site attribution.

  • 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, #28, and #30. Official feed formats: https://wordpress.com/support/feeds/

## Goal Let a user enter a public WordPress site or author archive URL and subscribe to the appropriate posts feed. ## Acceptance - Support the documented site feeds `/feed/` and `/feed/atom/`, plus author archive feeds `/author/name/feed/`. Support WordPress.com sites and verified self-hosted WordPress sites. - Validate that the selected feed represents the requested site or author. Do not select comments, tag/category feeds, or an entire site's posts when the user entered an author archive. - Preserve ActivityPub account detection where the site also supports federation. Offer the normal feed subscription/link choice for RSS/Atom setup. - Handle private/disabled/unavailable feeds and excerpt-only feeds. Present original post links and author/site attribution. - 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, #28, and #30. Official feed formats: https://wordpress.com/support/feeds/
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#35
No description provided.