Just discovered Ward Cunningham's new Spike Solution of Smallest Federated Wiki (P2P). The Smallest Federated Wiki project wants to be small in the "easy to learn powerful ideas" version of small. It wants to be a Wiki Engine so that strangers can meet and create works of value together. And it wants to be federated so that the burden of maintaining long-lasting content is shared among those who care... This project should be judged by the degree that it can: Demonstrate that wiki would have been better had it been effectively federated from the beginning. Explore federation policies necessary to sustain an open creative community. RuBy Personal Server (not Ruby On Rails). A step beyond WikiWeb, more oriented toward Creative Network Group Forming?
Big emphasis on Client Side rendering, which reminds me of Tiddly Wiki.
Does this assume that each node doesn't have to deal with NAT/FireWall issues? Not to mention that this assumes you have a machine that's AlwaysOn. Can this be run on Cheap Hosting?
Ward presented this at IndieWeb Camp (attendees). Rather than posting content on many third-party silos of content, we should all begin owning the content we're creating. Publish short status updates on your own domain, and syndicate to Twitter. Publish photos on your own domain, syndicate to Flickr, etc, etc. See z2009-06-03-DentPersonalContentRoot.
Everything is in GitHub.
Update: Ward posted some short videos.
GUI editor - drag paragraphs around (NodeWeb), even across pages - each node is a JSON element
- people's pages don't get merged together, they just get replicated.
"an internal link could be internal to the federation (WikiWeb), not just your own server"
Jan'2012: still working on it.