MikMik: Difference between revisions
| Line 39: | Line 39: | ||
'''Long-term shared |
'''Long-term shared namespaces''': |
||
A typical example would be a school of people all working together to build help documents, notes about their town, and class notes from their classes. While the total set of things everyone in town is working on might be larger than any individual wants to store on their own XO, they would at the same time want to browse this full collection from the school's collective cache. |
A typical example would be a school of people all working together to build help documents, notes about their town, and class notes from their classes. While the total set of things everyone in town is working on might be larger than any individual wants to store on their own XO, they would at the same time want to browse this full collection from the school's collective cache. |
||
Revision as of 21:27, 16 February 2008
see more templates or propose new |
MikMik currently supports local editing of a namespaces of interlinked wikipages, and synching of same with a shared namespace on other machines.
Adding support for a new wiki platform
- Provide a parser that can render your wiki's markup, and link to it from the discussion page.
- Wait.
- Wiki!
Please provide either a python or a javascript parser, or both if they exist. Currently under discussion: whether to handle rendering on the client side or otherwise.
Description & Goals
MikMik is a wiki built on top of the Bazaar distributed revision control system. In simple use, it acts like any number of simple wikis. However, it provides a text-specific "word-by-word" interface to difference reflection and resolution. More importantly, it provides a Javascript interface for conflict resolution.
The wiki currently supports the Markdown markup format with rudimentary support for Mediawiki markup as well.
The system targets the XO-1 and is currently undergoing testing and improvement and needs a better UI. There is currently a major known bug and some unresolved interface issues. UNICEF is doing related user interface work in coordination with the project.
TextNet was built by Benjamin Mako Hill as his Masters degree thesis at the MIT Media Lab.
- Initial package: MikMik-8.xo
Use cases
Single collaboration: A few users editing a single document together want to be able to edit on their own machines, push changes after each significant update, and transparently pull in changes from the others. This has different pros and cons than Abicollab -- it works well with frequent disconnections, it assumes there will be no forking, rather than forking by default when conflicts arise; and it provides an interface for visualizing and resolving merge conflicts.
Long-term shared namespaces:
A typical example would be a school of people all working together to build help documents, notes about their town, and class notes from their classes. While the total set of things everyone in town is working on might be larger than any individual wants to store on their own XO, they would at the same time want to browse this full collection from the school's collective cache.
MikMik server
Long-term shared namespaces, and pushing of edits out to the Internet from a regularly offline mesh of individuals, both work best with reliable, highly-connected, storage-rich MikMik nodes that can cache and forward and provide access to their public collections via http and like services for people without MikMik who wish to read and reuse resulting works.
Some use cases here include a scaling to ten thousand users, scaling to multiple schools, sharing 10GB of text, and a global Wikipedia interface.