Historic:PureContent - Revision history

Admin: Admin moved page PureContent to Historic:PureContent

2024-12-04T05:19:59Z

Admin moved page PureContent to Historic:PureContent

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

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

2016-09-27T20:52:17Z

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

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

Sir Finkus at 20:51, 27 September 2016

2016-09-27T20:51:42Z

← Older revision		Revision as of 20:51, 27 September 2016
Line 1:		Line 1:
			{{archival}}
	== Synopsis ==		== Synopsis ==

Art: /* Technology */

2014-02-08T15:27:41Z

Technology

← Older revision		Revision as of 15:27, 8 February 2014
Line 10:		Line 10:
	The central site would need to provide full contents of a story '''only''' to a "new" server. Then, only diffs, in the form of e.g. single moderations and comments, would suffice.		The central site would need to provide full contents of a story '''only''' to a "new" server. Then, only diffs, in the form of e.g. single moderations and comments, would suffice.

	The central site would be obliged to provide regular dumps, so that it could be replaced, if users vote to do so.		The central site would be obliged to provide regular dumps, so that it could be replaced, if users vote to do so. The dumps might be made from scratch only e.g. once a month. Then, only differential dumps would be made, only e.g. once a day.

	== Costs ==		== Costs ==

Art: /* Costs */

2014-02-08T15:27:27Z

Costs

← Older revision		Revision as of 15:27, 8 February 2014
Line 14:		Line 14:
	== Costs ==		== Costs ==
	The cost or running the central server would likely me minimal. A single moderation per second and a single comment each 10 seconds probably indicate quite a busy site, yet in terms of CPU and bandwidth usage, such values are almost negligible.		The cost or running the central server would likely me minimal. A single moderation per second and a single comment each 10 seconds probably indicate quite a busy site, yet in terms of CPU and bandwidth usage, such values are almost negligible.

			The dumps might be mirrored, for further decrease of costs.

Art at 15:24, 8 February 2014

2014-02-08T15:24:53Z

← Older revision		Revision as of 15:24, 8 February 2014
Line 7:		Line 7:
	== Technology ==		== Technology ==
	Dedicated protocols would likely be the most efficient ones, when it comes to minimising costs of running the central site.		Dedicated protocols would likely be the most efficient ones, when it comes to minimising costs of running the central site.

			The central site would need to provide full contents of a story '''only''' to a "new" server. Then, only diffs, in the form of e.g. single moderations and comments, would suffice.

	The central site would be obliged to provide regular dumps, so that it could be replaced, if users vote to do so.		The central site would be obliged to provide regular dumps, so that it could be replaced, if users vote to do so.

			== Costs ==
			The cost or running the central server would likely me minimal. A single moderation per second and a single comment each 10 seconds probably indicate quite a busy site, yet in terms of CPU and bandwidth usage, such values are almost negligible.

Art: /* Technology */

2014-02-08T15:12:39Z

Technology

← Older revision		Revision as of 15:12, 8 February 2014
Line 8:		Line 8:
	Dedicated protocols would likely be the most efficient ones, when it comes to minimising costs of running the central site.		Dedicated protocols would likely be the most efficient ones, when it comes to minimising costs of running the central site.

	The central site would be obliged to provide regular dumps, ~~and a method should~~ be ~~devised, which would allow to replace the central site~~, if users vote to do so.		The central site would be obliged to provide regular dumps, so that it could be replaced, if users vote to do so.

Art: /* Technology */

2014-02-08T14:55:19Z

Technology

← Older revision		Revision as of 14:55, 8 February 2014
Line 7:		Line 7:
	== Technology ==		== Technology ==
	Dedicated protocols would likely be the most efficient ones, when it comes to minimising costs of running the central site.		Dedicated protocols would likely be the most efficient ones, when it comes to minimising costs of running the central site.

			The central site would be obliged to provide regular dumps, and a method should be devised, which would allow to replace the central site, if users vote to do so.

Art at 14:52, 8 February 2014

2014-02-08T14:52:29Z

← Older revision		Revision as of 14:52, 8 February 2014
Line 1:		Line 1:
	== Synopsis ==		== Synopsis ==

	A central site would handle ~~contents~~, but would not distribute it massively as HTML. Instead, a streamlined "pure content" would be provided to a number of web servers, which would "skin" the content with whatever they would like. The servers might compete with their skins, but they might also put ads if they would wish. Anyway, it would be the users, which would decide which web server to choose.		A central site would handle content, but would not distribute it massively as HTML. Instead, a streamlined "pure content" would be provided to a number of web servers, which would "skin" the content with whatever they would like. The servers might compete with their skins, but they might also put ads if they would wish. Anyway, it would be the users, which would decide which web server to choose.

	In this way, the cost of running the central server would be reduced, and the main cost - bandwidth and HTML generation, would be distributed to the community.		In this way, the cost of running the central server would be reduced, and the main cost - bandwidth and HTML generation, would be distributed to the community.

	== Technology ==		== Technology ==
	Dedicated protocols would likely be most efficient, when it comes to minimising costs of running the central site.		Dedicated protocols would likely be the most efficient ones, when it comes to minimising costs of running the central site.

Art: Created page with "== Synopsis == A central site would handle contents, but would not distribute it massively as HTML. Instead, a streamlined "pure content" would be provided to a number of web..."

2014-02-08T14:51:26Z

Created page with "== Synopsis == A central site would handle contents, but would not distribute it massively as HTML. Instead, a streamlined "pure content" would be provided to a number of web..."

New page

== Synopsis ==

A central site would handle contents, but would not distribute it massively as HTML. Instead, a streamlined "pure content" would be provided to a number of web servers, which would "skin" the content with whatever they would like. The servers might compete with their skins, but they might also put ads if they would wish. Anyway, it would be the users, which would decide which web server to choose.

In this way, the cost of running the central server would be reduced, and the main cost - bandwidth and HTML generation, would be distributed to the community.

== Technology ==
Dedicated protocols would likely be most efficient, when it comes to minimising costs of running the central site.