change_instructions_navigator

The <a href="http://fed.wiki.org/view/about-federated-wiki">wiki</a> embodies <a href="http://c2.com/%7Eward/">Ward Cunningham</a>’s approach to <a href="https://www.youtube.com/watch?v=3Qccml0_o-s">solving complex, urgent problems</a> (analogous to Doug Engelbart’s <a href="https://1962paper.org">conceptual framework</a>). With the Wikipedia adopting his technology, I think it’s fair to say that he achieved a great deal of it (<a href="https://www.youtube.com/watch?v=XqxwwuUdsp4#t=14m34s">1</a>, <a href="https://www.youtube.com/watch?v=bx6nNqSASGo#t=1h30m43s">2</a>), himself having been inspired by <a href="https://skreutzer.de/2018/07/11/hypercard/">HyperCard</a>. In contrast to the popular <a href="https://en.wikipedia.org/wiki/MediaWiki">MediaWiki</a> software package, Ward’s most recent <a href="https://www.youtube.com/watch?v=ujMuu5ZDz18">wiki implementation</a> is <a href="https://www.youtube.com/watch?v=lDwTGEkKq_c">decentralized</a> in acknowledgement of the sovereignity, independence and autonomy of participants on the network. Contributions to a collective effort and the many different perspectives need to be federated of course, hence the name “<a href="http://ward.fed.wiki.org/view/chorus-of-voices">Federated Wiki</a>”. Ward’s Federated Wiki concept offers quite some unrealized potential when it comes to an Open Hyperdocument System and Ward is fully aware of it, which in itself is testament to the deep insights of his. The hypertext aspects don’t get mentioned too often in his talks, and why should they, work on (linked) data is equally important. Ward has some ideas for what we would call <a href="https://www.youtube.com/watch?v=mAM4_MUiCZQ#t=39m15s">ViewSpecs (39:15)</a>, <a href="https://www.youtube.com/watch?v=mAM4_MUiCZQ#t=41m30s">revision history (41:30)</a> – although more thinking could go into this, <a href="https://www.youtube.com/watch?v=mAM4_MUiCZQ#t=43m36s">federating (43:36)</a>, <a href="https://www.youtube.com/watch?v=mAM4_MUiCZQ#t=44m44s">capability infrastructure (44:44)</a> and the necessary libre-free licensing not only of the content, but also the corresponding <a href="https://www.youtube.com/watch?v=mAM4_MUiCZQ#t=45m46s">software (45:46-47:39)</a>. Beyond the Federated Wiki project, it might be beneficial to closely study other <a href="https://en.wikipedia.org/wiki/User:HaeB/Timeline_of_distributed_Wikipedia_proposals#Timeline_of_%22distributed_Wikipedia%22_proposals">wiki proposals</a> too. I guess it becomes pretty aparent that I need to start my own Federated Wiki instance as joining a wiki farm is probably not enough. I hate blogging because the way the text is stored and manipulated, but I keep doing it for now until I get a better system set up and because WordPress is libre-freely licensed software as well as providing APIs I can work with, so at some point in the future I’ll just export all of the posts and convert them to whatever the new platform/infrastructure will be. On the blog, capabilities like allowing others to correct/extend my texts directly are missing, similar to distributed source code management as popularized by <code>git</code>/GitHub (forking, pull requests). For now, I do some small experimentation on <a href="http://skreutzer.tries.fed.wiki">skreutzer.tries.fed.wiki</a>. This text is licensed under the <a href="https://www.gnu.org/licenses/agpl-3.0.html">GNU Affero General Public License 3 + any later version</a> and/or under the <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">Creative Commons Attribution-ShareAlike 4.0 International</a>.