So I left this to brew in my head for a while now, and it’s time to do a proper braindump.
The main idea is to have a completely community-edited archive, which is represented on Internet by a wiki-like storage with web-based interface.
The storage would consist of actual content and its metadata in a revision-tracked database.
The interface would provide everyone with an account access to perform actions on wiki drive. Possible actions include categorizing content, adding language tags, editing titles, modifying the content itself with updated files, etc.
Each of the actions that can be performed by a user does not take effect immediately. This gives other users a chance to confirm the action made by another user (sort of approve it) or perform a different or opposite action. When actions by two or more users are in conflict, the interface automatically opens up a discussion where users can reach an agreement. Once agreement is reached, all users will be asked to confirm the action that has been agreed upon. If no agreement is reached within a day, wiki drive automatically reverts all actions.
Curators (initially chosen by Outernet, later community-picked) oversee the actions in the wiki drive and approve actions that are conflict-free. Curators will still have the ability to deny actions even if they don’t have any conflicts, according to Outernet’s content guidelines (which will be published soon). Curators do not have the ability to perform any actions on the wiki drive, though, so they are strictly in oversight capacity.
Once a day, a cron job will sync all approved edits to the community library on Outernet.
To the extent allowed by security and privacy concerns, as well as common sense, wiki drive will have complete activity logs on a publicly accessible page and/or in downloadable format.
While we are going to work on wiki drive for sure, I would like to hear your comments first. Also, ideas on how to make this work today with existing tools, would also be nice.