marius@rimu this looks good.
I had trouble picturing your suggestion because I still have trouble thinking of ActivityPub S2S as a separate protocol from C2S, and as such I think of Activities as something only the actor themselves can create using their client.
So when I was thinking about activities with batched objects from multiple actors my brain broke. :D
This being only about servers announcing batches of activities to other servers as a communication back-channel makes more sense.
(I'm still unclear why the announce activities are needed, shouldn't the original activity already have reached all servers? but I feel like that's a lemmy problem rather)
All GNU social JP content and data are available under the