Here we dip into bleeding edge explorations in the wikiverse - stuff from Pioneers, that we wish we had the time to get into, and are way behind with. One day . .
Ward assembled yearbooks for each year of practice in the weekly wiki-hacking dojo: - Dojo Practices 2020 with diagrams - Dojo Practices 2021 with scripts - Dojo Practices 2022 with graphs
Dojo yearbooks wiki - ward.dojo.fed.wiki
This attempt to collect and understand the history of wiki, as well as its current facade, tries to remember the small nuances we pass by in inventing this hypertext medium. How federating works in wiki. Style matters.
We built the federation based on the promiscuous sharing of simple things with the hope that this would lead the community to save indefinitely things worth saving. Within a year we had moved from ruby to node without leaving ruby sites behind. Now, in the federation's ninth year, we consider how this process might be further distributed.
Through computer programs we construct large portions of our own future. Here we address how we might make faster and better decisions as we learn from and provide for each other. We draw from our own experience and those of Thompson Morrison and David Woods.
Wiki offers local and global versions of search. Global becomes more difficult as our federation grows. We explore possible proliferation of indexes over large regions that would benefit from incremental specialization possible with Outpost Thinking.
Disgust and Envy of academics to the advances in image processing of which style-transfer is representative. wiki 
Invitation to the Page Portal - open the page in firefox in a corner of your screen whenever you are reading or writing federated wiki.
# Push and pull in the wikiverse and fediverse
We suggest a new kind of content that can be created and shared within the federation with new rules for authorship and persistence. We intend this for fast distribution as one would expect in a conversation but with a well supported path to curated persistence expected of a wiki.
> **Channels:** Content added to a Channel by typing, speaking or dragging will find temporary residence within the server-side component where it can be replicated and distributed to all viewers of the item in units similar to those managed by Paragraph, Image, Audio and Video plugins.
> **Curating:** An author that chooses to selectively keep content from a Channel is thus curating their permanent record of the conversation. Other authors might choose differently and their choices are open to side-by-side viewing and copying as is our tradition.
> **Real-time distribution and subscription:** We expect remote channels to discover each other from hints in the fork history and from this establish a non-hierarchical real-time distribution network. Forking a Channel on to a new server is thus establishing a subscription to this network.
> **Affordances for conversation:** We might concoct new client-side affordances for generating conversationally useful items.
> **Latency = chat-speed:** There could be a natural delivery latency which make ephemeral content suitable for chat room behavior but would fall short of live conferencing.
# How to wiki on mobile devices
> We consider how an advanced handheld and networked device could connect people, place and method in purposeful collaboration. See Flutter Client
> We choose the specific application of sustainable urban design but suggest tooling that could apply to projects ranging from industrial to artistic.
A lineup of sophisticated stuff related to **Transformation visualiser** wiki
**09sep2021** matrix : I \[Ward] shared a diagram a week ago of my trails site drawn by following links and leaving out the trail pages that make up most of the site. That diagram showed the organization I had imposed over the the trail pictures without recognizing the automation that has emerged there over the last year.
We show how things can connect to wiki with low-latency websocket connections. A wiki page sends programs and retrieves data which it shares with other pages in the federation.
This system has its roots in an analysis of soil restoration as climate change intervention. pdf
Worker Environments are an adaptation of the Service Workers API, which is a browser standard for offline web applications. site