TryGhost / TryGhost/ActivityPub
Recommend object URL should 301 to AP resource
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 237
- Forks
- 35
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 60
Description
Earlier this month, I discovered that Ghost's latest blog post didn't make it into NodeBB, due to a bug on my end. I attempted to resolve it via URL but there was no AP resource at that URL. I ended up having to query the instance actor (which I happened to already know), and looking at the outbox.
There is some guidance here as to how to handle these types of situations.
But basically, if you're able to have Ghost serve the activity+json response for the URL (based on Accept header), that would be ideal. It's a common use-case for users of the open social web. If you cannot serve the activitypub payload on that same url, then a 302 redirect to the AP payload would also work great 😄
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Ghost object URLs are handled for ActivityPub requests, using the linked ActivityPub HTML discovery guidance and the Accept header behavior described in the issue. Verify that an object URL returns the ActivityPub response when requested with the appropriate media type, or redirects to the AP payload when it cannot do so.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100