You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to ActivityPub specification, servers should respond with ActivityStreams object representation to requests having application/ld+json; profile="https://www.w3.org/ns/activitystreams" in Accept header, but apparently only application/activity+json is supported
Servers ... MUST present the ActivityStreams object representation in response to application/ld+json; profile="https://www.w3.org/ns/activitystreams", and SHOULD also present the ActivityStreams representation in response to application/activity+json as well.
Thanks for pointing that out! Looks like those previous changes only encompassed the API endpoints, and not the canonical / public URLs for blogs and posts. That's all fixed in #779.
Activity
Correctly respond to application/ld+json requests
thebaer commentedon Sep 21, 2023
Thanks for reporting this! Fixed now, and will go into v0.14.
silverpill commentedon Sep 23, 2023
@thebaer I tried this:
But it returns HTML, not JSON.
The header value in #766 seems to be correct though. Perhaps the change wasn't included in 0.14?
Correctly respond to application/ld+json requests
Correctly respond to application/ld+json requests, part 2
thebaer commentedon Sep 26, 2023
Thanks for pointing that out! Looks like those previous changes only encompassed the API endpoints, and not the canonical / public URLs for blogs and posts. That's all fixed in #779.
silverpill commentedon Sep 27, 2023
Thank you for looking into this!
Has this patch been applied to any live instance where I can test it?
thebaer commentedon Oct 2, 2023
Yes, it's live on Write.as now!
silverpill commentedon Oct 3, 2023
Everything working as expected. Thanks a lot
thebaer commentedon Oct 3, 2023
Great, thank you for verifying!