This is clearly a change. I don't know if it's a regression. I don't like `activity.object` *sometimes* being an object and *sometimes* being a string with a URL, but --
[reading some specs]
-- okay, maybe this is fundamentally how JSON-LD works?
If that's the case, I feel like the thing to do is to run the document through a JSON-LD parser and say "give me `activity.object.content`, dereferencing links as necessary", but ... that doesn't seem to be what JSON-LD API actually does.
All the examples there are about different ways to serialize a graph using different "contexts", nowhere do they actually talk about expanding nodes from URLs.
This leaves me feeling like I'm missing a fundamental layer of the abstraction.
Ah shucks. I just realized, even if I want the client to dereference all these URLs, I *can't* do so on the browser side. Not the ones that are Mastodon-hosted, anyway. Because of the same bug that prevents fetching the outbox:
I'd need to bounce it through a proxy that has an HTTP client not shackled by CORS.
Maybe I need to start a bounty on that bug. Reading #Mastodon from a browser is hard.
A Mastodon instance for cats, the people who love them, and kindness in general. We strive to be a radically inclusive safe space. By creating an account, you agree to follow our CoC.