Jump to content

Decentralizing wiki technology: Difference between revisions

From IdeaWazaWiki
← Older edit

wikademia>Wikademia

wikademia>Remi
added see also and external links
wikademia>Wikademia
m Text replace - '__NOEDITSECTION__' to '<!--__-__-->'
 
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
'''Decentralizing Wikipedia and its sister projects''' is a project to create a framework of how decentralizing the technical details Wikimedia projects may work. This is just an intellectual exercise. It may or may not work in practice. It may or may not be practical, and it may or may not be a feasible method of reducing the load on central servers and allowing for greater capacity and empowerment of content and users, respectively. This could maybe be a fork of BOINC, GnuTella, or FreeNet or some synthesis of the aforementioned.
'''Decentralizing wiki technology''' is a project to formulate a framework of how to decentralize the subsystems of the various wiki projects.  


It might work something like the following. Anyone can setup tracker and content servers (that runs as part of [[Wikiversity Screen Saver]] or just as a service in the background). These servers and nodes track changes and where you can find articles on the network.
In practice, this project could perhaps be a fork of BOINC, GnuTella, OFFsystem or FreeNet or some synthesis of the aforementioned... or something else.
==Brainstorming==
It might work something like the following. Anyone can setup tracker and/or content server (that runs as part of [[Wikademia Screen Saver]], some other program, or just as a service in the background). These servers and nodes track changes and where you can find articles on the network.


Trackers could be large or small. They could be dedicated machines, or run in the background of peoples computers.
Trackers could be large or small. They could be dedicated machines, or run in the background of peoples' electronic devices.


For example, since Wikipedia is quite large, Wikipedia would probably have the most tracker servers.
For example, since Wikipedia is quite large, Wikipedia would probably have the most tracker servers.


Wikiversity would probably have considerably fewer, but could be dynamically balanced and tweaked according to need.
Wikademia would probably have a great deal fewer. All of this could be dynamically balanced and tweaked according to need.


When someone views an article, they basically ping the tracker server, saying in computer talk, "I want to see an article on Cows".
When someone wants to view an article on cows, they basically ping a tracker server, saying in computer talk, "I want to see an article on Cows".


Their machine could attempt to tell this to multiple tracker servers, and could hopefully get a rather speedy response.
Their machine could attempt to tell this to multiple tracker servers, and could hopefully get a rather speedy response.


===Trust===
The tracker server would say, "In order the amount of trust you can put into the integrity of the article, you can find the most up to date revision of the article on Cows on the servers x, y, z, and c".
The tracker server would say, "In order the amount of trust you can put into the integrity of the article, you can find the most up to date revision of the article on Cows on the servers x, y, z, and c".


Line 21: Line 25:
They make their changes and send them off to a few of the servers that contain the article on cows. This would then be propagated and perhaps reviewed by editors and then integrated into the best version.
They make their changes and send them off to a few of the servers that contain the article on cows. This would then be propagated and perhaps reviewed by editors and then integrated into the best version.


Maybe it could simply be integrated. Suppose someone came along and saw that it was vandalism. They could revert it as normally is done, and then that revert could be propigated.
Maybe it could simply be integrated. Suppose someone came along and saw that it was vandalism. They could revert it as normally is done, and then that revert could be propagated.


Maybe OpenID could be used to verify identities. That is an interesting challenge. How could identities be trusted on a decentralized system. OpenId?
Maybe OpenID could be used to verify identities. That is an interesting challenge. How could identities be trusted on a decentralized system. OpenId?


There could be separate nodes for images.
There could be separate nodes for images.
==Questions==
* Would a whole copy of the all the text be needed on servers?
* Could images and other media be stored in a more decentralized fashion?


==See also==
==See also==
* [[Meta:P2P]]
* [[Distributed P2P search engine]]
* [[P2P]]


==External links==
==External links==
* [http://www.gossamer-threads.com/lists/wiki/foundation/121420 'Possibility of a git-based fully distributed Wikipedia']]
* ''[http://www.gossamer-threads.com/lists/wiki/foundation/121420 Possibility of a git-based fully distributed Wikipedia]
* ''[http://torrentfreak.com/will-bittorrent-sites-become-obsolete-080530/ Will BitTorrent Sites Become Obsolete?]
* [http://offsystem.sourceforge.net/ Sourceforge: OffSystem] - A distributed owner-free file system
* March 2007 ''[http://www.globule.org/publi/DWECWH_webist2007.html A Decentralized Wiki Engine for Collaborative Wikipedia Hosting]
 
[[Category:Decentralization]]
<!--__-__-->
__NOTOC__

Latest revision as of 23:06, 30 September 2009

Decentralizing wiki technology is a project to formulate a framework of how to decentralize the subsystems of the various wiki projects.

In practice, this project could perhaps be a fork of BOINC, GnuTella, OFFsystem or FreeNet or some synthesis of the aforementioned... or something else.

Brainstorming

It might work something like the following. Anyone can setup tracker and/or content server (that runs as part of Wikademia Screen Saver, some other program, or just as a service in the background). These servers and nodes track changes and where you can find articles on the network.

Trackers could be large or small. They could be dedicated machines, or run in the background of peoples' electronic devices.

For example, since Wikipedia is quite large, Wikipedia would probably have the most tracker servers.

Wikademia would probably have a great deal fewer. All of this could be dynamically balanced and tweaked according to need.

When someone wants to view an article on cows, they basically ping a tracker server, saying in computer talk, "I want to see an article on Cows".

Their machine could attempt to tell this to multiple tracker servers, and could hopefully get a rather speedy response.

Trust

The tracker server would say, "In order the amount of trust you can put into the integrity of the article, you can find the most up to date revision of the article on Cows on the servers x, y, z, and c".

The person who requested the article on cows would then send a message off to machines x, y, z, and c". Hopefully, x would respond first, in a speedy manner and the article would pop up speedily.

Presuming this goes right, the individual may decide he or she would like to edit the article.

They make their changes and send them off to a few of the servers that contain the article on cows. This would then be propagated and perhaps reviewed by editors and then integrated into the best version.

Maybe it could simply be integrated. Suppose someone came along and saw that it was vandalism. They could revert it as normally is done, and then that revert could be propagated.

Maybe OpenID could be used to verify identities. That is an interesting challenge. How could identities be trusted on a decentralized system. OpenId?

There could be separate nodes for images.

Questions

  • Would a whole copy of the all the text be needed on servers?
  • Could images and other media be stored in a more decentralized fashion?

See also

Retrieved from "https://ideawaza.com/index.php?title=Decentralizing_wiki_technology&oldid=19521"