A property of federated wiki, is that as an author develops, she soon cends up creating many separate wikis, each with their own domain or sub-domain. This is a great feature, which soon requires managing using software tooling.
# Anarchive
The Anarchive is a new form of commons that we seek to develop together with others. It is a place where we permanently archive culturally relevant conversations.
# Rosters of Activity
Federate wiki currenlty allows us to view activity in wiki in powerful ways using the about roster plugin and the about activity plugin, however it can be slow and complicated to set these up and then maintain them.
# Managed Rosters
We admire the simplicity and robustenss of providing rosters of activity, that reflext a given point in time. Wiki's built in ability to version these rosters enables us to provide regular snapshots of the federations activity using complex machinary, but to publish these snapshots as loosely coupled wiki-pages which no longer depend on this machinary.
# Publishing Machinary
We view the role of this publishing machinary, as disposable, and as such it occupies a separate architectural layer of federated microservices that we call Platform Earth.
This layer allows us to engineer microservices in any language we like, using domain specfic languages, containers and bespoke operating systems, to author content, while preserving the simplicity and closeness to raw web standards of the federation for viewing, and federated authoring.
# See also