# 为什么据说是ActivityPub联邦的Discourse讨论串无法通过外部AP客户端访问？
**URL:** https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997
**Category:** Bug
**Tags:** activitypub
**Created:** [2025 年3 月 12 日 16:51 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997 "2025-03-12T16:51:58Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@roke\_julian\_lockhart](https://meta.discourse.org/u/roke_julian_lockhart)
#### Post date: [2025 年3 月 12 日 16:51 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/1 "2025-03-12T16:51:58Z")
#### 示例
如果我在 [`mastodon.social/search`](https://mastodon.social/search) 中输入 [`https://meta.discourse.org/t/uris-to-the-origin-of-a-thread-that-has-since-been-merged-should-503-to-the-merged-comment/342417?u=rokejulianlockhart`](https://meta.discourse.org/t/uris-to-the-origin-of-a-thread-that-has-since-been-merged-should-503-to-the-merged-comment/342417?u=rokejulianlockhart)（或 [`https://meta.discourse.org/ap/object/bc8f042ccca5ef56734c5f2460aa45cc`](https://meta.discourse.org/ap/object/bc8f042ccca5ef56734c5f2460aa45cc)）\[1\]，它会 404：\[2\] \[3\]
如果这不是 Discourse 的问题，我将把这个问题 [提交给 Mastodon](https://github.com/mastodon/mastodon/issues/new?template=2.server_bug_report.yml)。但是，我尝试过的大多数其他 AP 平台（我期望它们能正常工作）都工作正常。
* * *
1. [`https://meta.discourse.org/t/uris-to-the-origin-of-a-thread-that-has-since-been-merged-should-503-to-the-merged-comment/342417?u=rokejulianlockhart`](https://meta.discourse.org/t/uris-to-the-origin-of-a-thread-that-has-since-been-merged-should-503-to-the-merged-comment/342417?u=rokejulianlockhart)
2. [`search?q=https%3A%2F%2Fmeta.discourse.org%2Fap%2Fobject%2Fbc8f042ccca5ef56734c5f2460aa45cc`](https://mastodon.social/search?q=https%3A%2F%2Fmeta.discourse.org%2Fap%2Fobject%2Fbc8f042ccca5ef56734c5f2460aa45cc#:~:text=Posts-,No%20results.,-Explore)
3. [`search?q=https%3A%2F%2Fmeta.discourse.org%2Ft%2Furis-to-the-origin-of-a-thread-that-has-since-been-merged-should-503-to-the-merged-comment%2F342417%3Fu%3Drokejulianlockhart`](https://mastodon.social/search?q=https%3A%2F%2Fmeta.discourse.org%2Ft%2Furis-to-the-origin-of-a-thread-that-has-since-been-merged-should-503-to-the-merged-comment%2F342417%3Fu%3Drokejulianlockhart#:~:text=Posts-,No%20results.,-Explore)
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [2025 年5 月 4 日 08:40 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/3 "2025-05-04T08:40:37Z")
我也缺少这个。没有它，除非它们已经在你的时间线上，否则很难或不可能与联邦帖子互动。
@rokejulianlockhart，只是好奇，你是否尝试过使用带有 WP ActivityPub 插件的 WordPress 实例的 URL？
---
### Author:  [@RokeJulianLockhart1](https://meta.discourse.org/u/RokeJulianLockhart1)
#### Post date: [2025 年5 月 4 日 08:54 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/4 "2025-05-04T08:54:12Z")
这里到底发生了什么？我从来没有像下面这样写过：
RokeJulianLockhart：
> 在我们的论坛上讨论一下。
……而且有人把我的标记搞得一团糟。
---
### Author:  [@roke\_julian\_lockhart](https://meta.discourse.org/u/roke_julian_lockhart)
#### Post date: [2025 年5 月 4 日 08:54 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/5 "2025-05-04T08:54:56Z")
> [@RokeJulianLockhart1](#):
>
> 这里到底发生了什么？
哦！他们现在已经联合了！我不是在这里发表评论的。[comparación] 他们只是在联合方面出了点问题：
1. 格式没有被保留。
2. ~~我能够喜欢我自己的帖子。~~
这是一个单独的用户帐户，因为它是在另一个域上注册的。
[^1]：[`socialhub.activitypub.rocks/t/5123/3`](https://socialhub.activitypub.rocks/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/5123/3?u=rokejulianlockhart)
> [@icaria36](#):
>
> @rokejulianlockhart，我只是好奇，你是否尝试过使用带有 WP ActivityPub 插件的 WordPress 实例的 URL？
@icaria36，没有。你知道有任何吗？
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [2025 年5 月 4 日 09:02 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/6 "2025-05-04T09:02:59Z")
我相信这是一个 WordPress 网站，我刚刚用一篇最新的文章进行了测试，确实可以在 Mastodon 上找到该网址：[Nature Holds Awe, Man – NHAM Mixtape 11 – NHAM](https://nham.co.uk/2025/05/nature-holds-awe-man-nham-mixtape-11/)
---
### Author:  [@roke\_julian\_lockhart](https://meta.discourse.org/u/roke_julian_lockhart)
#### Post date: [2025 年5 月 4 日 09:06 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/7 "2025-05-04T09:06:13Z")
@icaria36，我不这么认为。Discourse 有原生的 AP 集成。
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [2025 年5 月 4 日 09:09 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/8 "2025-05-04T09:09:10Z")
@rokejulianlockhart 针对您创建此主题的观点，同时，`https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997` 在 Mastodon 上找不到。
---
### Author:  [@roke\_julian\_lockhart](https://meta.discourse.org/u/roke_julian_lockhart)
#### Post date: [2025 年5 月 4 日 09:22 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/9 "2025-05-04T09:22:51Z")
> [@icaria36](#):
>
> `https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997` 在 Mastodon 上找不到。
@icaria36，那可能是 Mastodon 的问题，因为 Discourse 会将其联合：
> **[Why is Discourse content inaccessible? · mastodon/mastodon · Discussion #34600](https://github.com/mastodon/mastodon/discussions/34600#discussion-8278099)**
>
> Although meta.discourse.org/t/356997/8 is federated via ActivityPub to alternative Discourse instances, like socialhub.activitypub.rocks/t/5123/7, the URI is inaccessible at every Mastodon instance...
---
### Author:  [@roke\_julian\_lockhart](https://meta.discourse.org/u/roke_julian_lockhart)
#### Post date: [2025 年5 月 5 日 12:31 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/10 "2025-05-05T12:31:39Z")
[`github.com/mastodon/mastodon/discussions/34600#discussioncomment-13031935`](https://github.com/mastodon/mastodon/discussions/34600#discussioncomment-13031935:~:text=Collaborator-,The%20Discourse%20AP%20plugin%20makes,correct%20Accept%20content%20negotiation%20header.,-Unmark%20as%20answer) 指出：
> Discourse AP 插件会在您点击绿色的 ActivityPub 图标并点击「笔记」按钮复制 URL 时，使 ActivityPub 对象可用：[https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991](https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991)
>
> Discourse AP 需要以某种方式将 `url` 链接回 `id`，最好是通过在带有正确 `Accept` 内容协商头的请求上进行重定向来实现。
~~因此，我将暂时将此标记为 #contribute:bug。~~ （我无法操作。该议题已过期。）
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [2025 年5 月 5 日 19:32 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/11 "2025-05-05T19:32:16Z")
但是“Notes”图标提供的 URL 粘贴到 [`mastodon.social/search`](https://mastodon.social/search) 等地方时，不会返回任何结果。
问题未解决。
---
### Author:  [@roke\_julian\_lockhart](https://meta.discourse.org/u/roke_julian_lockhart)
#### Post date: [2025 年5 月 5 日 19:46 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/12 "2025-05-05T19:46:12Z")
@icaria36，请在 GitHub Discussion 中评论此事。让其他人对回复提出质疑比我作为联络人更有说服力。
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [2025 年5 月 7 日 07:12 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/13 "2025-05-07T07:12:18Z")
> [@rokejulianlockhart](#):
>
> 那可能是Mastodon的错误
看起来是这样：
>
>
> \### Steps to reproduce the problem
>
> Call \`/api/v2/search\` with \`resolve=true\` fo…r a \`q\`uery of a Discourse post -- for example, https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991
>
> \### Expected behaviour
>
> The object should be resolved as a Status
>
> \### Actual behaviour
>
> The search returns no results
>
> \### Detailed description
>
> Per https://browser.pub/https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991 the payload is as follows:
>
> \`\`\`http
> HTTP/1.1 200 OK
> cache-control: no-cache, no-store
> cf-cache-status: DYNAMIC
> cf-ray: 93bd1fc4d4df6773-ATL
> connection: keep-alive
> content-type: application/activity+json; charset=utf-8
> cross-origin-opener-policy: same-origin
> date: Wed, 07 May 2025 02:00:30 GMT
> referrer-policy: strict-origin-when-cross-origin
> server: cloudflare
> strict-transport-security: max-age=31536000
> transfer-encoding: chunked
> vary: Accept
> x-content-type-options: nosniff
> x-discourse-route: discourse\_activity\_pub/ap/objects/show
> x-frame-options: SAMEORIGIN
> x-permitted-cross-domain-policies: none
> x-request-id: d70bb69f-bf6b-4084-9d6a-342fa1c33df9
> x-xss-protection: 0
>
> {
> "id": "https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991",
> "type": "Note",
> "audience": "https://meta.discourse.org/ap/actor/a1ba34f9dd25f8ad96ce6efcbfb931e5",
> "to": \[
> "https://www.w3.org/ns/activitystreams#Public",
> "https://meta.discourse.org/ap/actor/a1ba34f9dd25f8ad96ce6efcbfb931e5"
> \],
> "cc": \[
> "https://meta.discourse.org/ap/actor/a1ba34f9dd25f8ad96ce6efcbfb931e5"
> \],
> "published": "2025-05-04T09:22:51Z",
> "updated": "2025-05-04T09:22:51Z",
> "url": "https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/9",
> "attributedTo": "https://meta.discourse.org/ap/actor/d721191fe3a461470f2dbbf85c1cc98e",
> "context": "https://meta.discourse.org/ap/collection/0a5f1ca375b3dd95ce3e810e567f305c",
> "content": "icaria36:\\\https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997\ cannot be found on Mastodon.\\\@icaria36, it's probably a fault of Mastodon's, then, since Discourse federates it:\\\https://github.com/mastodon/mastodon/discussions/34600#discussion-8278099\\\\\Discuss this on our forum.\",
> "inReplyTo": "https://meta.discourse.org/ap/object/fda0d57b504bbfdfd91ec1f80bce1742",
> "@context": "https://www.w3.org/ns/activitystreams"
> }
> \`\`\`
>
> The only things that look potentially off to me are:
>
> \- The \`Content-Type\` header has a \`charset=utf-8\` parameter on it
> \- The addressee \`https://meta.discourse.org/ap/actor/a1ba34f9dd25f8ad96ce6efcbfb931e5\` is present in both \`to\` and \`cc\`
>
> \### Mastodon instance
>
> mastodon.social
>
> \### Mastodon version
>
> v4.4.0-nightly.2025-05-07-security
>
> \### Technical details
>
> \_No response\_
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [2025 年5 月 7 日 11:34 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/14 "2025-05-07T11:34:24Z")
嗯，不，这似乎最终还是一个 Discourse 的 bug：[Posts from Discourse do not resolve via the Search API · Issue #34632 · mastodon/mastodon · GitHub](https://github.com/mastodon/mastodon/issues/34632#issuecomment-2858004832)
> 进一步调查发现，Mastodon 使用以下 `Accept` 标头请求资源：
>
> ```plaintext
> Accept: application/activity+json, application/ld+json; profile="https://www.w3.org/ns/activitystreams", text/html;q=0.1
>
> ```
>
> 使用此标头查询 discourse 会导致 HTTP 400 响应。
>
> 忽略 `text/html;q=0.1` 会返回一个 ActivityStreams 对象。因此，这似乎是 Discourse 的一个 bug，当 `text/html` 是可接受类型的一部分时，它似乎会返回 400……
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [2025 年5 月 9 日 09:18 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/15 "2025-05-09T09:18:23Z")
@rokejulianlockhart 或者管理员，能否请你们移除“已解决”标签？并根据 Mastodon 在 [Posts from Discourse do not resolve via the Search API · Issue #34632 · mastodon/mastodon · GitHub](https://github.com/mastodon/mastodon/issues/34632#issuecomment-2858004832) 上的评估，将此话题移至 #Contribute > Bug（或创建一个新的错误报告）。
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [2025 年5 月 19 日 15:50 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/16 "2025-05-19T15:50:07Z")
我不确定这是 Discourse 中的一个错误。我已经在 Mastodon 上回复了这个问题。为了方便起见，在此处交叉发布：
> 在那种情况下，我们返回 400 的原因是 ActivityPub 规范 [似乎要求它](https://www.w3.org/TR/activitypub/#server-to-server-interactions)。
>
> > POST 请求（例如发送到收件箱）必须使用 `application/ld+json; profile="https://www.w3.org/ns/activitystreams"` 的 Content-Type 进行，GET 请求（另请参阅 [3.2 检索对象](https://www.w3.org/TR/activitypub/#retrieving-objects)）则使用 `application/ld+json; profile="https://www.w3.org/ns/activitystreams"` 的 Accept 标头。
>
> [@ClearlyClaire](https://github.com/ClearlyClaire) 是否需要在 `Accept` 标头中添加 `text/html;q=0.1`？
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [2025 年5 月 20 日 08:11 UTC](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/17 "2025-05-20T08:11:36Z")
此问题将很快得到解决。请参阅：
>
>
> \### Steps to reproduce the problem
>
> Call \`/api/v2/search\` with \`resolve=true\` fo…r a \`q\`uery of a Discourse post -- for example, https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991
>
> \### Expected behaviour
>
> The object should be resolved as a Status
>
> \### Actual behaviour
>
> The search returns no results
>
> \### Detailed description
>
> Per https://browser.pub/https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991 the payload is as follows:
>
> \`\`\`http
> HTTP/1.1 200 OK
> cache-control: no-cache, no-store
> cf-cache-status: DYNAMIC
> cf-ray: 93bd1fc4d4df6773-ATL
> connection: keep-alive
> content-type: application/activity+json; charset=utf-8
> cross-origin-opener-policy: same-origin
> date: Wed, 07 May 2025 02:00:30 GMT
> referrer-policy: strict-origin-when-cross-origin
> server: cloudflare
> strict-transport-security: max-age=31536000
> transfer-encoding: chunked
> vary: Accept
> x-content-type-options: nosniff
> x-discourse-route: discourse\_activity\_pub/ap/objects/show
> x-frame-options: SAMEORIGIN
> x-permitted-cross-domain-policies: none
> x-request-id: d70bb69f-bf6b-4084-9d6a-342fa1c33df9
> x-xss-protection: 0
>
> {
> "id": "https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991",
> "type": "Note",
> "audience": "https://meta.discourse.org/ap/actor/a1ba34f9dd25f8ad96ce6efcbfb931e5",
> "to": \[
> "https://www.w3.org/ns/activitystreams#Public",
> "https://meta.discourse.org/ap/actor/a1ba34f9dd25f8ad96ce6efcbfb931e5"
> \],
> "cc": \[
> "https://meta.discourse.org/ap/actor/a1ba34f9dd25f8ad96ce6efcbfb931e5"
> \],
> "published": "2025-05-04T09:22:51Z",
> "updated": "2025-05-04T09:22:51Z",
> "url": "https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/9",
> "attributedTo": "https://meta.discourse.org/ap/actor/d721191fe3a461470f2dbbf85c1cc98e",
> "context": "https://meta.discourse.org/ap/collection/0a5f1ca375b3dd95ce3e810e567f305c",
> "content": "icaria36:\\\https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997\ cannot be found on Mastodon.\\\@icaria36, it's probably a fault of Mastodon's, then, since Discourse federates it:\\\https://github.com/mastodon/mastodon/discussions/34600#discussion-8278099\\\\\Discuss this on our forum.\",
> "inReplyTo": "https://meta.discourse.org/ap/object/fda0d57b504bbfdfd91ec1f80bce1742",
> "@context": "https://www.w3.org/ns/activitystreams"
> }
> \`\`\`
>
> The only things that look potentially off to me are:
>
> \- The \`Content-Type\` header has a \`charset=utf-8\` parameter on it
> \- The addressee \`https://meta.discourse.org/ap/actor/a1ba34f9dd25f8ad96ce6efcbfb931e5\` is present in both \`to\` and \`cc\`
>
> \### Mastodon instance
>
> mastodon.social
>
> \### Mastodon version
>
> v4.4.0-nightly.2025-05-07-security
>
> \### Technical details
>
> \_No response\_
>
>
> See further: https://github.com/mastodon/mastodon/issues/34632#issuecomment-2893…266537