Is Content Negotiation planned for the main ghost CMS or will it remain a distinct service?

[bumblefudge]

Issue Summary

I noticed today that curling blog pages with either of the ActivityPub "Accept: " headers returns just the regular HTML version of that blog post, not the AP version. Is it on the roadmap to make the CMS do content negotiation? Would a custom reverse-proxy config for extracting JSON-LD and/or JSON AP replies from the DB be an easier lift than fully integrating AP into the CMS?

Steps to Reproduce

1. navigate to the URL of a specific blog post.
2. curl that URL with the AP Accept headers

(tested on both ghost.com and self-hosted)

Ghost Version

6-alpine

Node.js Version

whatever 6-alp uses

How did you install Ghost?

docker compose

Database type

MySQL 5.7

Browser & OS version

No response

Relevant log / error output

Code of Conduct

• I agree to be friendly and polite to people in this repository

[gobengo]

curl -H "Accept: application/ld+json; profile="https://www.w3.org/ns/activitystreams"" 'https://blog.identity.foundation/dif-welcomes-aven-hospitality/'

curl -H "Accept: application/ld+json; profile="https://www.w3.org/ns/activitystreams"" 'https://blog.identity.foundation/author/dif/'

Expected Behavior:

• response body is parseable as JSON

Actual Behavior

• response content-type is text/html
• response body is not parseable as JSON

[muratcorlu]

Is this a common behavior on other ActivityPub supporting blogging platforms? What is the intention here to fetch a blog post as an JSON LD?