Sometimes remote instances require all requests to be signed

[fauno]

(We're asking the instance admin if we can name it publically)

We're testing remote follows from a Mastodon+Glitch v4.1.3 instance and it fails because it requires signed requests to fetch Actors. We can reproduce by curling the follower profile:

curl --header "Accept: application/activity+json" FOLLOWER_PROFILE_URL | jq .

Returns:

{
  "error": "Request not signed"
}

[fauno]

It's related to this feature:

https://docs.joinmastodon.org/admin/config/#authorized_fetch

https://fedi.tips/authorized-fetch/

[fauno]

Action: All requests should be signed, or feature detection is needed to discover which instances require signed requests

[RangerMauve]

Cool, yes that is very doable.

[RangerMauve]

@akhileshthite Basically we need to replace the call to this.fetch with this.signedFetch

https://github.com/hyphacoop/social.distributed.press/blob/initial/src/server/apsystem.ts#L187

[akhileshthite]

@akhileshthite Basically we need to replace the call to this.fetch with this.signedFetch

https://github.com/hyphacoop/social.distributed.press/blob/initial/src/server/apsystem.ts#L187

Do we need a test named getActor fetches and returns the actor profile using signedFetch for this?

[RangerMauve]

Merged into latest initial branch!