And a short summary how the federation works:
Main objects in terms of federation are the
InstanceandArticle. Each article belongs to a single origin instance, the one where it was originally created. Articles have a collection ofEdits a custom ActivityPub type containing a diff. The text of any article can be built by starting from empty string and applying all associated edits in order. Instances can synchronize their articles with each other, and follow each other to receive updates about articles. Edits are done with diffs which are generated on the backend, and allow for conflict resolution similar to git. Editing also works over federation. In this case an activityUpdate/Editis sent to the origin instance. If the diff applies cleanly, the origin instance sends the new text in anUpdate/Articleactivity to its followers. In case there is a conflict, aRejectactivity is sent back, the editor needs to resolve and resubmit the edit.