News for hackers. Stuff that matters.
Re:Verizon/Yahoo Blocking Attempts to Archive Yahoo Groups –... by dredmorbius on Monday December 09, 2019 @06:15AM (#21741754)
Maintaining a static archive is remarkably inexpensive. The total amount of textual data included in even Google+ was likely only a few hundred GB. Images and multimedia, of course, would have been far more, though sampling-based estimates suggest that these were a few hundred KB each, on average, on about 30% of all posts.

The mean post size on G+ was rougly the same as on Twitter: about 120 characters. (Quite possibly because most G+ posts were themselves repurposed Twitter content.)

Static content does not require ongoing moderation, though it's possible that problematic content will be periodically identified.

The bigger challenge is actually in the publishing engines. Even where these are static, it's possible that vulnerabilities will be identified. That was Google's (not especially convincing) excuse.

A challenge of the Internet Archive / Archive Team method of archival and access is that in preserving the original formatting and packaging of content, the bandwidth and storage requirements are increased tremendously. By about two orders of magnitude in the case of G+.

Were the Archive to focus on the actual originally-authored content rather than all the associated chrome, both factors would be tremendously reduced.

There are no comments on this comment yet.