Skip to content

micropub: Micropub extensions roadmap (maturity-grouped) #354

Description

@davidwkeith

Tracking issue for adopting the IndieWeb Micropub extensions in @dwk/micropub.

The wiki organizes extensions into three maturity groupsofficial (adopted into the spec), stable (widely implemented and settled), and proposed (experimental). @dwk/micropub mirrors that model: each extension is tagged with its group and only advertised/honoured when that group is enabled, via the extensions config ({ official?, stable?, proposed? }; defaults official+stable on, proposed off).

Stable — implemented ✅ (this increment)

  • Post Status (post-status: published/draft) — validated on create/update
  • Visibility (visibility: public/unlisted/private) — validated; stored & advertised only, read-time enforcement is the serving layer's job
  • Supported Vocabulary (post-types in q=config via postTypes config)
  • Category/Tag List (q=category) with Limit (limit) and Filter (filter)
  • Slug (mp-slug) — pre-existing, always on
  • Destination (mp-destination) — declined: our model is one Worker = one site with a single-user me binding, so multi-destination has no meaning unless that changes

Stable — tracked separately

Proposed — off by default, roadmap

Notes

  • Serving-layer boundary: @dwk/micropub stores and advertises post-status/visibility; it does not itself gate reads. Hiding drafts and access-controlling private posts belong to the consuming site (or WAC in @dwk/solid-pod).
  • DPoP posture is unchanged by any of this: the default bearer-only micropub.rocks flow still can't authenticate; extensions improve real-client capability, they don't move the conformance bar.

See spec/packages/micropub.md § "Micropub extensions" for the authoritative requirements.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions