155 |
|
|
156 |
(The Internet Archive's Wayback Machine [waybackmachine]_ |
(The Internet Archive's Wayback Machine [waybackmachine]_ |
157 |
alleviates these concerns, but it introduces |
alleviates these concerns, but it introduces |
158 |
a single point of failure for the *entire* Web!) |
a single point of failure (XXX and censorship) for the *entire* Web!) |
159 |
|
|
160 |
.. <<<We don't propose that every byte of information ever published |
.. <<<We don't propose that every byte of information ever published |
161 |
on the Web has to be kept around forever. However, |
on the Web has to be kept around forever. However, |
380 |
Applications |
Applications |
381 |
============ |
============ |
382 |
|
|
383 |
A File-shared, Decentralized, Heterogeneous Web |
**A File-shared, Decentralized, Heterogeneous Web.** |
384 |
----------------------------------------------- |
The main application we see for pointer records |
385 |
|
is the implementation of a file-shared web |
386 |
|
in a distributed, decentralized and above all |
387 |
|
*heterogeneous* way. |
388 |
|
|
389 |
|
|
390 |
- standardizing on pointer records such as ours, |
- standardizing on pointer records such as ours, |
391 |
can provide full static-page (no CGI, no servlet) |
can provide full static-page (no CGI, no servlet) |
412 |
|
|
413 |
- should be possible to attach metadata to pointers |
- should be possible to attach metadata to pointers |
414 |
|
|
415 |
- a surprise benefit: distributed wayback machine |
**A distributed wayback machine.** |
416 |
|
a surprise benefit: distributed wayback machine |
417 |
|
|
418 |
- as long as anyone has a copy, ... |
- as long as anyone has a copy, ... |
419 |
|
|
423 |
|
|
424 |
|
|
425 |
|
|
426 |
Software / media updates |
**Software / media updates.** |
427 |
------------------------ |
Distributed apt-get / windows update |
|
|
|
|
- distributed apt-get / windows update |
|
428 |
|
|
429 |
- obvious bandwidth savings |
- obvious bandwidth savings |
430 |
|
|