Well, as I said before, an Announce is an Announce. By which I mean, when you send an Announce, that is semantically a “reshare” of the original object. Your Announce activity gets added to the shares
collection on that object.
If you would like to reshare something with an additional comment, then your options are:
Announce Note
, but include additional content
on the Announce
.
In this case, most fedi projects don’t understand content
on Announce
, so your activity will “fall back” to just being a boost/retweet/etc of the original object/post. Your comment won’t be visible anywhere in those projects.
id: <some-reshare>
actor: <you>
type: Announce
content: "This is my comment" # most projects will ignore this
object:
id: <some-post>
attributedTo: <someone>
content: "Original post"
Create Note
as usual, but insert a link and then tag
that Link
with extra metadata.
In this case, most fedi projects understand a Create Note
to mean posting a status. This will “fall back” to being a status with a link effectively copypasted in. As a progressive enhancement, some projects like Foundkey will understand “object links” (a la FEP-e232) and open those links in-app rather than in a new browser tab. Additionally, if you use the right link relation, the link can be understood as a “quote post” according to Misskey semantics, and Foundkey will embed a preview of the linked post when rendering your own post.
id: <some-create>
actor: <you>
type: Create
object:
id: <your-post>
attributedTo: <you>
content: "This is my comment. RE: <quoted-post>"
tag:
- href: <quoted-post>
# per FEP-e232, we hint that this link can be fetched as an activitypub object
mediaType: application/ld+json; profile="https://www.w3.org/ns/activitystreams"
# for Foundkey, we hint that this is a "quote" as understood by Misskey
rel: ["https://misskey-hub.net/ns#_misskey_quote"]
See FEP-e232: Object Links - #34 by trwnh for more