logoalt Hacker News

__MatrixMan__yesterday at 6:16 PM2 repliesview on HN

This is a fundamental flaw in the web. Since we treat a server's name as authoritative, anybody maintaining a replica needs to repeatedly hit that server to know if their remote version is up to date.

If we trusted digital signatures on content instead of server names, we could have a model where a single bit of server load propagates to millions of interested parties. As it is the server must do something distinct for each interested party.

CDNs mitigate this only partially, because mutable data means they have no good cache invalidation strategy.

There's got to be a solution that doesn't involve heaping even more burdensome requirements on those who would dare to publish.


Replies

dennis-trayesterday at 6:26 PM

Content-addressing decouples the hoster from the data itself. Anyone can serve content-addressed data and you can locally verify that you’ve got served the correct bytes. IPFS implements building blocks for such an alternative web.

What irony that this article is about crawling content-addressed data.

show 1 reply
inigyouyesterday at 7:51 PM

Or poll a merkle tree root hash, like, um, git