Historic:Distributed - Revision history

Admin: Admin moved page Distributed to Historic:Distributed

2024-12-04T05:19:51Z

Admin moved page Distributed to Historic:Distributed

← Older revision	Revision as of 05:19, 4 December 2024
(No difference)

Sir Finkus: Protected "Distributed" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2016-09-27T20:51:09Z

Protected "Distributed" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 20:51, 27 September 2016
(No difference)

Sir Finkus at 20:51, 27 September 2016

2016-09-27T20:51:01Z

← Older revision		Revision as of 20:51, 27 September 2016
Line 1:		Line 1:
			{{archival}}
	A few proposals on distributed architecture, that would allow to maintain independency and sharing of costs.		A few proposals on distributed architecture, that would allow to maintain independency and sharing of costs.

Janek Kozicki at 19:52, 7 February 2014

2014-02-07T19:52:28Z

← Older revision		Revision as of 19:52, 7 February 2014
Line 3:		Line 3:
	* [[Synced servers\|Synced servers style]];		* [[Synced servers\|Synced servers style]];
	* [[Bit-torrent style]].		* [[Bit-torrent style]].
			* [[Bitcloud style]].

Art at 15:55, 7 February 2014

2014-02-07T15:55:23Z

← Older revision		Revision as of 15:55, 7 February 2014
Line 1:		Line 1:
	A few proposals on distributed architecture, that would allow to maintain independency and sharing of costs.		A few proposals on distributed architecture, that would allow to maintain independency and sharing of costs.

	* [[Synced servers\|Synced servers style]]		* [[Synced servers\|Synced servers style]];
	* [[Bit-torrent style]]		* [[Bit-torrent style]].

Art at 15:50, 7 February 2014

2014-02-07T15:50:14Z

← Older revision		Revision as of 15:50, 7 February 2014
Line 1:		Line 1:
	A few proposals on distributed architecture, that would allow to maintain independency and ~~share~~ costs.		A few proposals on distributed architecture, that would allow to maintain independency and sharing of costs.

	* [[Synced servers\|Synced servers style]]		* [[Synced servers\|Synced servers style]]
	* [[Bit-torrent style]]		* [[Bit-torrent style]]

Art: Replaced content with "A few proposals on distributed architecture, that would allow to maintain independency and share costs. * Synced servers style * Bit-torrent style"

2014-02-07T15:43:02Z

Replaced content with "A few proposals on distributed architecture, that would allow to maintain independency and share costs. * Synced servers style * Bit-torrent style"

@@ Line 1: / Line 1: @@
-== Synopsis ==
+A few proposals on distributed architecture, that would allow to maintain independency and share costs.
 * [[Synced servers|Synced servers style]]
 * [[Bit-torrent style]]

Art at 15:41, 7 February 2014

2014-02-07T15:41:09Z

← Older revision		Revision as of 15:41, 7 February 2014
Line 15:		Line 15:
	* users can vote on chosing a new central server.		* users can vote on chosing a new central server.

	* [[Synced servers style]]		* [[Synced servers\|Synced servers style]]
	* [[Bit--torrent style]]		* [[Bit-torrent style]]

Art at 15:40, 7 February 2014

2014-02-07T15:40:34Z

← Older revision		Revision as of 15:40, 7 February 2014
Line 14:		Line 14:
	* important data is mirrored outside the central server; this includes authentication data, but excludes low-importance and often changing data like mod points;		* important data is mirrored outside the central server; this includes authentication data, but excludes low-importance and often changing data like mod points;
	* users can vote on chosing a new central server.		* users can vote on chosing a new central server.

			* [[Synced servers style]]
			* [[Bit--torrent style]]

Art at 15:17, 7 February 2014

2014-02-07T15:17:07Z

← Older revision		Revision as of 15:17, 7 February 2014
Line 12:		Line 12:

	While centralising authentication and user data would make things much simpler, a special care should be given to limitting of permissions of the central server owners. For example, it might be an inherent part of the protocol, that:		While centralising authentication and user data would make things much simpler, a special care should be given to limitting of permissions of the central server owners. For example, it might be an inherent part of the protocol, that:
	* important data is mirrored outside the central server; this includes authentication data, but excludes low-importance~~, yet highly variable~~ data like mod points;		* important data is mirrored outside the central server; this includes authentication data, but excludes low-importance and often changing data like mod points;
	* users can vote on chosing a new central server.		* users can vote on chosing a new central server.