M
@thisismissem I don't ascribe to the semiotic theory of the web where the map is not the territory.
I like to keep things simple and therefore a json-ld document is a valid representation of an object that can exist as a binary.
People keep forgetting that ActivityPub is meant to be used on top of other web standards like content negotiation.
@oranadoz cool, cool. That's indeed what I meant. 
@oranadoz you say "indeed" but you end up contradicting me.
Why do you think the server should not return a json-ld document if asked for one?
@hongminhee I would assume the same URL can represent both a PNG image and a JSON-LD document.
Here's how I do it in ONI.
The URL https://releases.bruta.link/icon represents the icon for the application actor found at https://releases.bruta.link.
If you fetch it using an Accept header for a json+ld document, that's what you'll get, if you ask it for an image/* document, then you'll get the raw image.
So, from a client point of view, the server returns the raw image, unless asked specifically for a JSON-LD document.
Also at this pace I might run out of things to document if my NGI0 grant proposal will be approved, as a lot of the deliverables I set are for decreasing the friction new developers will have in using the library, which relies heavily on good documentation. 
It's a nice problem to have I guess.
Writing documentation was good for #GoActivityPub.
It gives me the opportunity to go through some user scenarios for the tools I'm documenting and make sure that they work the way I'm describing.
I've fixed a couple of issues in this way these past days.
https://man.sr.ht/~mariusor/go-activitypub/go-ap/pitfalls.md#changing-the-type-of-an-object