[bawolff]

Reading through, this doesn't sound like a "federated wikipedia"

It sounds more like they want to implement the github fork & pull-request model of version control where currently Wikipedia uses a more SVN type of version control.

There are pros and cons to both models. However federation it is not. The mentioned controversies also seem entirely unrelated to which model you like.

[mdaniel]

I'm for sure not a federation nor ActivityPub ninja, but as I understand it due to the broadcast nature of ActivityPub and this project's "send updates to the origin server as patches" approach, then it is the opposite of both github and Subversion in that there is not one canonical hostname, and any one hostname doesn't, itself, contain 100% of the content, same as infosec.social for sure doesn't contain 100% of Mastodon content but I can read infosec.social posts on my.mastodon.example by subscribing to feeds that interest me. I currently can't (that I know of) submit patches to their Toots as reply activity, but I don't believe there's anything in the spec that would prevent such a thing, either

I'm keeping an eye on https://docs.gitlab.com/ee/architecture/blueprints/activity_... <https://news.ycombinator.com/item?id=39201453> with acute interest because I'm totally open to not even being able to see the ways federation can make ecosystems more valuable due to my lack of hands-on experience with the kinds of problems it is solving