gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/pointers article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/pointers article.rst
Date: Mon, 10 Nov 2003 15:05:29 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/10 15:05:29

Modified files:
        pointers       : article.rst 

Log message:
        Reviewing with Tuomas

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/article.rst.diff?tr1=1.245&tr2=1.246&r1=text&r2=text

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.245 
manuscripts/pointers/article.rst:1.246
--- manuscripts/pointers/article.rst:1.245      Mon Nov 10 15:03:01 2003
+++ manuscripts/pointers/article.rst    Mon Nov 10 15:05:28 2003
@@ -550,11 +550,11 @@
    an issue as the pointer records' signatures could be validated.
 
 The peer-to-peer Web we propose would use
-random-looking, semantic-free identifiers; arguments for this
+semantic-free identifiers; arguments for this
 are discussed in [balakrishnan03semanticfree]_.
 
 **A distributed wayback machine.**
-A surprising benefit of pointer records is that
+One benefit of pointer records is that
 a file-shared web would *automatically* work
 as an enormous, distributed wayback machine.
 As long as anyone has a copy of a particular version
@@ -562,7 +562,7 @@
 To ensure archival, libraries or other institutions
 could easily make a P2P network of servers 
 ensuring that all relevant blocks
-would be archived. Unlike with the Wayback Machine,
+would be archived. Unlike with the Wayback Machine [waybackmachine]_,
 there would be no difficulty in setting up or accessing
 the system because it could use the exact same technologies
 as the rest of the file-shared web, simply configured slightly




reply via email to

[Prev in Thread] Current Thread [Next in Thread]