ActivityPub 연동이 supposedly 된 Discourse 스레드가 외부 AP 클라이언트에서 접근할 수 없는 이유는 무엇인가요?

[roke_julian_lockhart (Mr Beedell, Roke Julian Lockhart)]

Example

If I enter 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 (or https://meta.discourse.org/ap/object/bc8f042ccca5ef56734c5f2460aa45cc) ^[1] into mastodon.social/search, it 404s: ^{[2] [3]}

If this isn’t Discourse’s fault, I’ll take this to Mastodon. However, most other AP platforms that I’ve tried (that I’ve expected to work) have worked.

---

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 ↩︎

2. search?q=https%3A%2F%2Fmeta.discourse.org%2Fap%2Fobject%2Fbc8f042ccca5ef56734c5f2460aa45cc ↩︎

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 ↩︎

[icaria36]

I’m missing this as well. Without this, it is hard or impossible to interact with federated posts unless they are in your timeline already.

@roke_julian_lockhart, just curious, have you tried with URLs of WordPress instances using the WP ActivityPub plugin?

[RokeJulianLockhart1 (Mr. Beedell, Roke Julian Lockhart)]

What the heck has occurred here? I have never written like the undermentioned:

RokeJulianLockhart:

Discuss this on our forum.

...and someone's taken a sledgehammer to my markup.

[roke_julian_lockhart (Mr Beedell, Roke Julian Lockhart)]

@RokeJulianLockhart1

What the heck has occurred here?

Oh! They’re federated now! I didn’t post that comment here. ^[1] They’re merely rather broken in their federation:

1. The formatting isn’t conserved.

2. I am able to like my own posts.

   It’s a separate user account, since it’s registered on another domain.

@icaria36

@roke_julian_lockhart, just curious, have you tried with URLs of WordPress instances using the WP ActivityPub plugin?

@icaria36, no. Do you know of any?

---

1. socialhub.activitypub.rocks/t/5123/3 ↩︎

[icaria36]

I believe this is a WordPress site, and I just tested with a recent article, and I can find the URL on Mastodon indeed: Nature Holds Awe, Man – NHAM Mixtape 11 – NHAM

[roke_julian_lockhart (Mr Beedell, Roke Julian Lockhart)]

@icaria36, I don’t think so. Discourse has native AP integration.

[icaria36]

@roke_julian_lockhart To your point when you created this topic, meanwhile, https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997 cannot be found on Mastodon.

[roke_julian_lockhart (Mr Beedell, Roke Julian Lockhart)]

@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:

meta.discourse.org/t/356997/8 - Why is Discourse content inaccessible? ·...

[roke_julian_lockhart (Mr Beedell, Roke Julian Lockhart)]

github.com/mastodon/mastodon/discussions/34600#discussioncomment-13031935에서 다음과 같이 언급하고 있습니다:

Discourse AP 플러그인은 녹색 ActivityPub 로고를 클릭한 후 “Note” 버튼을 눌러 URL을 복사하면 ActivityPub 객체를 사용할 수 있게 합니다: https://meta.discourse.org/ap/object/5874fad7df806caa1fe34c382c1d2991

Discourse AP는 url이 id로 되돌아가도록 해야 하며, 가능하면 올바른 Accept 콘텐츠 협상 헤더를 가진 요청에 대해 리다이렉트를 통해 처리하는 것이 좋습니다.

따라서 이 문제를 일시적으로 #contribute:bug로 설정하겠습니다. (할 수 없습니다. 너무 오래되었습니다.)

[icaria36]

But the URLs provided by the “Notes” icon don’t throw any results when pasted on i.e. mastodon.social/search.

Problem not solved.

[roke_julian_lockhart (Mr Beedell, Roke Julian Lockhart)]

@icaria36, please comment that on the GitHub Discussion. Having someone else challenge the response lends some more credibility than having me be the liason.

[icaria36]

@roke_julian_lockhart

it’s probably a fault of Mastodon’s, then

Looks like that:

https://github.com/mastodon/mastodon/issues/34632

[icaria36]

Well, no, it seems that it might be a Discourse bug after all: Posts from Discourse do not resolve via the Search API · Issue #34632 · mastodon/mastodon · GitHub

Investigating a bit more, Mastodon requests the resource with the following Accept header:

Accept: application/activity+json, application/ld+json; profile="https://www.w3.org/ns/activitystreams", text/html;q=0.1

Querying discourse with this results in the HTTP 400 response.

Omitting the text/html;q=0.1 returns an ActivityStreams object. So this seems to be a bug with Discourse, which seems to return a 400 anytime text/html is part of the accepted types…

[icaria36]

@roke_julian_lockhart 또는 관리자분, "Solution"을 제거해 주시겠어요? 그리고 Posts from Discourse do not resolve via the Search API · Issue #34632 · mastodon/mastodon · GitHub Mastodon 평가에 따라 이 주제를 #contribute:bug로 이동하거나(또는 새로운 버그 리포트를 생성해 주세요).

[angus (Angus McLeod)]

I’m not sure this is a bug in Discourse. I’ve responded on the issue on Mastodon. Cross posting here for convenience:

The reason we return a 400 in that scenario is that the ActivityPub spec seems to require it.

POST requests (eg. to the inbox) MUST be made with a Content-Type of application/ld+json; profile=“ActivityStreams 2.0 Terms” and GET requests (see also 3.2 Retrieving objects) with an Accept header of application/ld+json; profile=“ActivityStreams 2.0 Terms”

@ClearlyClaire Is there a need to add text/html;q=0.1 to the Accept header?

[angus (Angus McLeod)]

This will be resolved soon. See further:

https://github.com/mastodon/mastodon/issues/34632#issuecomment-2892159150

https://github.com/discourse/discourse-activity-pub/pull/219