In many cases, remote JSON-LD documents have to be loaded to parse/canonicalize JSON-LD documents.
This is the case for outbound statuses, which require at least https://w3id.org/security/v1, https://www.w3.org/ns/activitystreams, and https://w3id.org/identity/v1.
The last one is currently unavailable, so any instance not having it in cache is currently screwed.
Such documents used to be bundled with Mastodon, but that was reverted in d40ef1129e6df5098e150ff3f6ee4eda9b7efcf8. I don't think saving a few MB of RAM was worthwhile here.
In many cases, remote JSON-LD documents have to be loaded to parse/canonicalize JSON-LD documents.
This is the case for outbound statuses, which require at least
https://w3id.org/security/v1,https://www.w3.org/ns/activitystreams, andhttps://w3id.org/identity/v1.The last one is currently unavailable, so any instance not having it in cache is currently screwed.
Such documents used to be bundled with Mastodon, but that was reverted in d40ef1129e6df5098e150ff3f6ee4eda9b7efcf8. I don't think saving a few MB of RAM was worthwhile here.