P2P Wiki: Difference between revisions

From P2P Foundation
Jump to navigation Jump to search
(Minor link corrections from last edit)
(Reorganized text and headings, revisioned and added content.)
Line 1: Line 1:
==What's a P2P wiki==  
==What's a P2P Wiki==  


A peer-to-peer wiki is a serverless decentralized wiki, hosted, edited, administrated and operated by its users. Imagine git (or another DCVS) but with asynchronous and ''realtime'' text editing, a p2p conflict management system, and a user-friendly interface. P2P wikis redefine how we publish, edit and administrate, text (among other potential things) on the internet.
A peer-to-peer wiki is a serverless decentralized wiki, hosted, edited, administrated and operated by its users. Imagine git (or another DCVS) but with asynchronous and ''realtime'' text editing, a p2p conflict management system, and a user-friendly interface. P2P Wikis redefine how we publish, edit, host and administrate text document type pages (among other things) on the internet.


==Why P2P Wikis?==
==Differences to existing text collaboration systems==
==Differences to similar software types==
* Realtime or asynchronous (Online and offline editing).
* Realtime or asynchronous
* Full revision history with playback.
* Full revision history with playback
* Merging, forking, branching of text/documents; allows a panarchical political meta-structure,like in the (FLOSS) software world.
* Merging, forking, branching text (for offline or online work)
* P2P conflict management.
* True p2p architecture
* True P2P Architecture
* P2P conflict management; panarchical political structure.
 
====The Blogosphere and Political Economy====
Blogs (and personal websites) generally administer, edited and publish content autocratically--a blogger often controls the servers too. While bloggers do add p2p or quasi-democratic elements to a blog, like p2p comment administering, they largely don't adopt an overall cooperative-type political structure.  


===Blogging And Poltical Economy==
Wikis are generally administered more democratically. And (large ones) are funded and operated by quasi-democratic non-profit foundations. Despite this, because of the centralized nature of current wiki technologies, large Wikis in particular, have somewhat autocratic political structure. This is a consequence of the structure of the web and internet, other things, as it stands today. P2P Wikis change that. It's political meta-structure is analogous to a [panarchy].  
Blogs generally administer, edited and publish content autocratically--a blogger even controls the servers, largely. While bloggers do add minor p2p or democratic elements to a blog, like p2p comment administering, they largely don't adopt a more cooperative political structures.


Wikis are generally administer more democratically, and are funded and operated by foundations. But p2p wikis go further, it's total political structure is analogous to a [panarchy].
==Why P2P Wikis?==
You can have a private page on say "Abraham Lincoln" solely expressing your viewpoint; analogous to a hermetic autocracy. You can publicly share the page and only give write access to a small group of known like-minded peers; that's like tribal band-sized anarchy. Branching, merging, or forking of content allows many types of social organization ecologies.


You can have private page on say, Abraham Lincoln, solely expressing your viewpoint. Share a public version of the page and edited with solely  like-minded people. Branch, merge, or fork from other version of "Abraham Lincoln" that exist.
====The Blogosphere's Enclosing of the Knowledge Commons====
The conceptualization and crediting ideas and insights to one's name, accrues status, social recognition/reputational benefits to oneself. As this process accumulates, one is eventually regarded as an expert, guru or authority. A mass following or personality cult can develop around the individual. This encloses the knowledge commons. And it rearranges political, economic and cultural organization for the interests of individuals, who often copyright the work. This is a process that largely goes unnoticed.


===The blogosphere's enclosing of the knowledge commons===
Wiki's see knowledge differently. While a single individual can make large and unequal contributions relative to others, the work is ultimately credited and possessed (or owned) by all--copylefted with collectively possesion.
Crediting ideas and insights to one's name, accrues status or social recognition to oneself. Overtime one is seen as an expert, guru or authority. and can gain a mass following or personality cult. This is a form of enclosing the knowledge commons, political, economic and cultural to individuals, who often copyright the work.


Wiki's see knowledge differently. While a single individual can make large and unequal contributions relative to others, the work is ultimately credited and possessed (or owned) by all; copylefted.
====Blogs and the Self-Help World: A Case Study of Political Enclosure====
The personal development, self-help, new age and lifestyle design field is broadly organized around individuals' books and websites/blogs. That creates the grounds for a meta-structure of competing autocracies in that world. It commonly revolved around popular figures with mass following of highly emulative and adulative followers. Popular figures derive power primarily from perceived expertise and knowledge. But both followers and the leader can't see the socio-political-cultural implications of a personality cult type structure. In fact, it they believe their social relations are completely democratic. In reality it is part authoritarian. #[http://p2pfoundation.net/Spiritual_Projection_and_Authority] #[http://p2pfoundation.net/Authoritarian_Blight_in_Spirituality]


==Approaches to creating a P2P Wiki==
==Approaches to creating a P2P Wiki==
Line 27: Line 30:
One approach to doing this is using a [https://en.wikipedia.org/wiki/Distributed_revision_control distributed revision control system] as a backend of the wiki, in peer-to-peer style. With this approach, there is no central store of the wiki's content; instead, every user can keep a complete copy of the wiki locally, and the software handles merging and propagating of changes when they are made. This is the approach taken by the [https://en.wikipedia.org/wiki/Ikiwiki ikiwiki] engine (which can use the distributed revision control system [https://en.wikipedia.org/wiki/Git_%28software%29Git] as its back-end), and [https://en.wikipedia.org/wiki/Code_Co-op Code Co-op] (a distributed revision control system that includes a wiki component).
One approach to doing this is using a [https://en.wikipedia.org/wiki/Distributed_revision_control distributed revision control system] as a backend of the wiki, in peer-to-peer style. With this approach, there is no central store of the wiki's content; instead, every user can keep a complete copy of the wiki locally, and the software handles merging and propagating of changes when they are made. This is the approach taken by the [https://en.wikipedia.org/wiki/Ikiwiki ikiwiki] engine (which can use the distributed revision control system [https://en.wikipedia.org/wiki/Git_%28software%29Git] as its back-end), and [https://en.wikipedia.org/wiki/Code_Co-op Code Co-op] (a distributed revision control system that includes a wiki component).


There has also been research done on allowing Wikipedia to be run as a decentralized wiki,<ref>[http://www.globule.org/publi/DWECWH_webist2007.html A Decentralized Wiki Engine for Collaborative Wikipedia Hosting], Guido Urdaneta, Guillaume Pierre and Maarten van Steen, ''Proceedings of the 3rd International Conference on Web Information Systems and Technology (WEBIST)'', March 2007</ref><ref>[http://www.globule.org/publi/WWADH_comnet2009.html Wikipedia Workload Analysis for Decentralized Hosting], Guido Urdaneta, Guillaume Pierre, Maarten van Steen, ''Elsevier Computer Networks 53(11)'', pp. 1830-1845, July 2009</ref> and on modifying the application XWiki to function in this way.<ref>[http://concerto.xwiki.com/xwiki/bin/view/Main/WebHome XWiki Concerto Project homepage]</ref>. And there other approaches: modifying Apache (formerly Google Wave), web apps like Etherpad, or desktop text editing software like [https://en.wikipedia.org/wiki/SubEthaEdit SubEthaEdit]. None of these technologies integrate all the features of a p2p wiki, as of yet.  
There's research on decentralized hosting of Wikipedia. And there are other angles to attack the problem: modifying Apache (formerly Google Wave) or web apps like Etherpad, and desktop text editing software like [https://en.wikipedia.org/wiki/SubEthaEdit SubEthaEdit]. None of these technologies integrate all the features of a p2p wiki, as of yet.  


====Projects====
===Projects===
*[https://en.wikipedia.org/wiki/Ikiwiki A serverless wiki]
*[https://en.wikipedia.org/wiki/Ikiwiki A serverless wiki]
*[https://github.com/github/gollum Gollum, a git wiki]
*[https://github.com/github/gollum Gollum, a git wiki]
Line 37: Line 40:
*[http://bouillon.math.usu.ru/index.html%3Fp=128.html Project Boullion, an Apache Wave like project]
*[http://bouillon.math.usu.ru/index.html%3Fp=128.html Project Boullion, an Apache Wave like project]


==== External Links/Discussions ====
===External Links/Discussions ===
*[http://meatballwiki.org/wiki/PeerToPeerWiki Meatball on P2P wikis]
*[http://meatballwiki.org/wiki/PeerToPeerWiki Meatball Wiki on P2P wikis]
*[http://c2.com/cgi/wiki?DistributedWiki C2 wiki's article and discussion]
*[http://c2.com/cgi/wiki?DistributedWiki C2 wiki's article and discussion]
*[http://www.globule.org/publi/DWECWH_webist2007.html Research paper on decentralizing Wikipedia]
*[http://www.globule.org/publi/DWECWH_webist2007.html Research paper on decentralizing Wikipedia]

Revision as of 02:03, 12 July 2012

What's a P2P Wiki

A peer-to-peer wiki is a serverless decentralized wiki, hosted, edited, administrated and operated by its users. Imagine git (or another DCVS) but with asynchronous and realtime text editing, a p2p conflict management system, and a user-friendly interface. P2P Wikis redefine how we publish, edit, host and administrate text document type pages (among other things) on the internet.

Differences to existing text collaboration systems

  • Realtime or asynchronous (Online and offline editing).
  • Full revision history with playback.
  • Merging, forking, branching of text/documents; allows a panarchical political meta-structure,like in the (FLOSS) software world.
  • P2P conflict management.
  • True P2P Architecture

The Blogosphere and Political Economy

Blogs (and personal websites) generally administer, edited and publish content autocratically--a blogger often controls the servers too. While bloggers do add p2p or quasi-democratic elements to a blog, like p2p comment administering, they largely don't adopt an overall cooperative-type political structure.

Wikis are generally administered more democratically. And (large ones) are funded and operated by quasi-democratic non-profit foundations. Despite this, because of the centralized nature of current wiki technologies, large Wikis in particular, have somewhat autocratic political structure. This is a consequence of the structure of the web and internet, other things, as it stands today. P2P Wikis change that. It's political meta-structure is analogous to a [panarchy].

Why P2P Wikis?

You can have a private page on say "Abraham Lincoln" solely expressing your viewpoint; analogous to a hermetic autocracy. You can publicly share the page and only give write access to a small group of known like-minded peers; that's like tribal band-sized anarchy. Branching, merging, or forking of content allows many types of social organization ecologies.

The Blogosphere's Enclosing of the Knowledge Commons

The conceptualization and crediting ideas and insights to one's name, accrues status, social recognition/reputational benefits to oneself. As this process accumulates, one is eventually regarded as an expert, guru or authority. A mass following or personality cult can develop around the individual. This encloses the knowledge commons. And it rearranges political, economic and cultural organization for the interests of individuals, who often copyright the work. This is a process that largely goes unnoticed.

Wiki's see knowledge differently. While a single individual can make large and unequal contributions relative to others, the work is ultimately credited and possessed (or owned) by all--copylefted with collectively possesion.

Blogs and the Self-Help World: A Case Study of Political Enclosure

The personal development, self-help, new age and lifestyle design field is broadly organized around individuals' books and websites/blogs. That creates the grounds for a meta-structure of competing autocracies in that world. It commonly revolved around popular figures with mass following of highly emulative and adulative followers. Popular figures derive power primarily from perceived expertise and knowledge. But both followers and the leader can't see the socio-political-cultural implications of a personality cult type structure. In fact, it they believe their social relations are completely democratic. In reality it is part authoritarian. #[1] #[2]

Approaches to creating a P2P Wiki

One approach to doing this is using a distributed revision control system as a backend of the wiki, in peer-to-peer style. With this approach, there is no central store of the wiki's content; instead, every user can keep a complete copy of the wiki locally, and the software handles merging and propagating of changes when they are made. This is the approach taken by the ikiwiki engine (which can use the distributed revision control system [3] as its back-end), and Code Co-op (a distributed revision control system that includes a wiki component).

There's research on decentralized hosting of Wikipedia. And there are other angles to attack the problem: modifying Apache (formerly Google Wave) or web apps like Etherpad, and desktop text editing software like SubEthaEdit. None of these technologies integrate all the features of a p2p wiki, as of yet.

Projects

External Links/Discussions