feat: route context fetch through the comments proxy #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/proxy-integration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Wire the widget to proxy/. A new
proxysetting(params.activitypub_comments.proxy, or per-post comments.proxy) makes
the JS fetch the context from
{proxy}/api/v1/statuses/{id}/contextinstead of directly from the instance — needed for auth-required
instances like GoToSocial. Display links (toot URL, avatars) still use
host, so they keep pointing at the real instance.proxy, emit data-proxy when setotherwise), and that display host is unchanged
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
Wire the widget to proxy/. A new `proxy` setting (params.activitypub_comments.proxy, or per-post comments.proxy) makes the JS fetch the context from `{proxy}/api/v1/statuses/{id}/context` instead of directly from the instance — needed for auth-required instances like GoToSocial. Display links (toot URL, avatars) still use `host`, so they keep pointing at the real instance. - partial: resolve `proxy`, emit data-proxy when set - js: fetch base = proxy || https://host; strips trailing slashes - hugo.toml + README + proxy/README + CLAUDE.md: document the wiring - exampleSite: add via-proxy CI fixture - ci.yml: assert data-proxy is emitted when configured (and absent otherwise), and that display host is unchanged Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>