#cwebber2> One or more "tags" that have been associated with an objects. A tag can be any kind of Object. The key difference between attachment and tag is that the former implies association by inclusion, while the latter implies associated by reference.
#cwebber2so I assume that means I should make them a proper object
#rhiarowould like to know what's expected but will continue to do what's useful without adding extra complication unless necessary for something cool
#rhiaroI have a post about submitting post-like activities via micropub up shortly..
#cwebber2{"@type": "Image", "@id": <web-page that contains the image and also a comment link and stuff>, "url": [{<thumbnail image, pointing with href>}, {<full image, pointing with href>}]
#cwebber2so the "url" in this case has multiple links, not just one
#rhiaroI really feel that's over abstracted, but I suppose I should keep my trap shut until I come up with something else
#cwebber2rhiaro: I'd love to see an alternative on the "mediagoblin *page*, with multiple image size links"
#rhiarothough I think elf dropped a link to mine in one of his emails
jasnell and cwebber2 joined the channel
#oshepherd_I still want to kill the post activity, IMO all it does is maximize redundancy...
#cwebber2oshepherd_: I've been thinking about that
#cwebber2oshepherd_: I guess the one nice thing about it that it seems like is the activity becomes a general envelope?
#cwebber2and maybe having an envelope separate from its contents is good?
#cwebber2but you have much more implementation experience than I do
#oshepherd_I think if you remove the "post" activity then what you find is that activities are encodings of state transitions, and actually ActivityStreams' model then matches up very well with e.g. mf2
#oshepherd_Also the ACLs being attached to the activity is demonstrably a massive issue as seen in pump.io