@tom a quick check list for you:

1. Check if the actor is publicly accessible from the internet.

2. Check if it has a RSA private/public key.

3. Check that if you have a proxy in front of ONI it doesn't mangle Accept/Vary/Content-Type headers.

4. Check that if you have a proxy the `/.well-known/webfinger` route is handled by ONI. (your proxy should forward all routes to ONI directly as a start)

@tom looking at the post of mine you linked, I realize you're probably thinking of regular object discovery, and there isn't any mechanism for it yet, or for viewing remote objects that haven't reached your inbox.

@tom I basically follow actors and that's how seeing posts by others in your /inbox works.

The frontend loads stuff directly through JavaScript fetch and needs all the mechanisms of that to work (and I imagine what you see might be things failing to load due to CORS rules being too restrictive on remote Mastodon instances)

I am not aware of any issues with receiving activities though, and in this process the objects themselves should be fully dereferenced to local copies.

I'll add a note about BOX compilation. Thanx.

@tom if it doesn't work out I'd also be interested in learning why not.

@tom check if this one I wrote can be of use:

https://github.com/mariusor/oni

PS: Any feedback about setting it up and configuring it for your use case will be appreciated, either here, or on github/mailing list.