# Waarom zijn zogenaamd ActivityPub-gefederde Discourse-threads ontoegankelijk via externe AP-clients?

**URL:** https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997
**Category:** Bug
**Tags:** activitypub
**Created:** [12 maart 2025 om 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:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [19 mei 2025 om 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")

</div>

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](https://www.w3.org/TR/activitypub/#server-to-server-interactions).
> 
> > POST requests (eg. to the inbox) MUST be made with a Content-Type of application/ld+json; profile=“[ActivityStreams 2.0 Terms](https://www.w3.org/ns/activitystreams)” and GET requests (see also [3.2 Retrieving objects](https://www.w3.org/TR/activitypub/#retrieving-objects)) with an Accept header of application/ld+json; profile=“[ActivityStreams 2.0 Terms](https://www.w3.org/ns/activitystreams)”
> 
> [@ClearlyClaire](https://github.com/ClearlyClaire) Is there a need to add `text/html;q=0.1` to the `Accept` header?

---

_[View the full topic](https://meta.discourse.org/t/why-are-supposedly-activitypub-federated-discourse-threads-inaccessible-via-external-ap-clients/356997)._