Warum sind angeblich federierte ActivityPub-Diskussionsthreads über externe AP-Clients nicht zugänglich?

angus · 20. Mai 2025 um 08:11

Dies wird bald behoben sein. Weitere Informationen finden Sie unter:

github.com/mastodon/mastodon

Posts from Discourse do not resolve via the Search API

opened 02:05AM - 07 May 25 UTC

closed 12:01PM - 21 May 25 UTC

trwnh

api activitypub

### 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:<blockquote><code>https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997</code> cannot be found on Mastodon.</blockquote>@icaria36, it's probably a fault of Mastodon's, then, since Discourse federates it:<a href=\"https://github.com/mastodon/mastodon/discussions/34600#discussion-8278099\">https://github.com/mastodon/mastodon/discussions/34600#discussion-8278099</a> <a href=\"https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997/9\">Discuss this on our forum.</a>", "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_

Thema		Antworten	Aufrufe
Forum federation thread on the.socialmusic.network General activitypub	24	403	5. Juli 2025
ActivityPub Plugin Plugin experimental , activitypub	457	44545	10. Dezember 2025
Replies from the Fediverse not visible in Discourse: "Perhaps this topic was closed or deleted while you were looking at it?" Support activitypub	3	55	1. April 2025
Federation support for Discourse Feature completed	122	37922	17. Mai 2024
How to debug connectivity issues with ActivityPub Administrators activitypub	23	394	11. März 2025

Warum sind angeblich federierte ActivityPub-Diskussionsthreads über externe AP-Clients nicht zugänglich?

Verwandte Themen