@benpate

I do believe that it's part of ActivityPub, because that's exactly the usecase: there's an object you're currently seeing and you want to interact with it.

I'm no AP dev, I have no experience at all, only armchair ideas so my goal isn't to say what you're doing is bad; quite the contrary, you're building stuff so you'ro certainly more relevant ! I'm just commenting on the sidelines.

The thing I like about the idea of AP is that it is about manipulation and exchange of data structures, whereas the APIs are about RPCs. I like that because it makes my data more portable, less dependent on an implementation or an instance.

What I would love to see is the AP concept more widespread for interacting:
- when I see content I want to interact with, my user agent can pick the object url in the http headers and/or in a <link> tag if it's presented in an html document
- my user-agent allows me to send AP activities, optionally linking to object urls

This obviously requires changes in the browser (which is where Mozilla should put its brain but that's another discussion), but can be first done in an extension. Bonus: it works for *all* AP implementations
@tchambers