550 |
an issue as the pointer records' signatures could be validated. |
an issue as the pointer records' signatures could be validated. |
551 |
|
|
552 |
The peer-to-peer Web we propose would use |
The peer-to-peer Web we propose would use |
553 |
random-looking, semantic-free identifiers; arguments for this |
semantic-free identifiers; arguments for this |
554 |
are discussed in [balakrishnan03semanticfree]_. |
are discussed in [balakrishnan03semanticfree]_. |
555 |
|
|
556 |
**A distributed wayback machine.** |
**A distributed wayback machine.** |
557 |
A surprising benefit of pointer records is that |
One benefit of pointer records is that |
558 |
a file-shared web would *automatically* work |
a file-shared web would *automatically* work |
559 |
as an enormous, distributed wayback machine. |
as an enormous, distributed wayback machine. |
560 |
As long as anyone has a copy of a particular version |
As long as anyone has a copy of a particular version |
562 |
To ensure archival, libraries or other institutions |
To ensure archival, libraries or other institutions |
563 |
could easily make a P2P network of servers |
could easily make a P2P network of servers |
564 |
ensuring that all relevant blocks |
ensuring that all relevant blocks |
565 |
would be archived. Unlike with the Wayback Machine, |
would be archived. Unlike with the Wayback Machine [waybackmachine]_, |
566 |
there would be no difficulty in setting up or accessing |
there would be no difficulty in setting up or accessing |
567 |
the system because it could use the exact same technologies |
the system because it could use the exact same technologies |
568 |
as the rest of the file-shared web, simply configured slightly |
as the rest of the file-shared web, simply configured slightly |