Six years ago we summarized for the ACM's forward looking conference, Splash, the design principles that had guided our work up to that point. These still hold today. Here we consider what we have learned since and suggest what might guide a rewrite.
See Federated Wiki Design Principles from 2014.
We may not be so clear regarding future principles but we have maintained some vision and now recognize tactics that will help us move forward.
# Vision
We Dream Big so we must begin by identifying those dreams that should not wait any longer. We've ignored those dreams that can be realized with plugins. We order the remainder from fundamental to necessary.
Computational Habitat as landscape for wiki.
How We Connect Data between pages.
Three Layer Storage factoring network responsibility.
Contours of Privilege controlling our things.
Organizing Large Communities hosted on wiki.
Search over the Horizon by extending the neighborhood.
Landing Page Registration for small groups or classes.
Login to View for schools or companies.
Beyond Slugs for identifying pages.
Journal Optimization to save space and clutter.
CSS Cascade that makes sense for pages and plugins.
Ephemeral Content creation, distribution and persistence.
Wiki Nature for VR won't be another video game.
# Tactics
We've learned that operating a server is getting progressively harder, not easier. Here we consider how our software architecture can make this approachable with basic web skills.
Farm is the Only Option.
Popular Clients in CDN or App Stores.
API Only Definition of Server.
ES6 Module Plugins
Foundation Maintains Standards.
Forever Free and Decentralized
.
Also see
Paul's R&D work with the Hypercore Protocol version of FedWiki. > As the commandline [dat] tool is no longer a driving force for the development of the protocol, it is becoming increasingly clear that more fine-grained control and modularity is needed.