4 ms·

How is this distributed model going to deal with the fact that a lot of (all of?) the websites we visit have dynamic content? I feel like I'd be much better of

by wang_li 11y ago

How is this distributed model going to deal with the fact that a lot of (all of?) the websites we visit have dynamic content? I feel like I'd be much better off, privacy-wise, if I could get a browser that had a user manageable list of locations to pre-cache with some kind of daily/weekly offline cache refresh. So when I go to a web page that fetches jquery from google's hosted libraries service, it instead pulls it from a locally cached copy and never ever fetches from google as a result of visiting a web page.

onion2k 11y ago
How is this distributed model going to deal with the fact that a lot of (all of?) the websites we visit have dynamic content? Web content is rarely very dynamic. With the exception of social networks and news sites, most websites would be largely indistinguishable from what they look like now if they were serving the same page as yesterday or a week ago. Technologically we could trade the 'rendered on request' model with the very latest data for a 'rendered and then cached across the internet for a day' distributed model very easily. Psychologically however, no one would agree to it. People believe their content has to be available to everyone the instant they press Publish.
- mrsharpoblunto 11y ago
  I disagree - aside from blog sites or marketing/portfolio type sites basically every web application on the modern internet requires per-user dynamic content to function - e-commerce, banking, productivity apps, social networks, messaging etc. the modern web is all about displaying and processing users data. Really any distributed cache is only going to be useful as a replacement for existing CDN's serving static assets (and thats totally fine - it would be great to see the democratization of the performance & scalability of a global CDN)
- collyw 11y ago
  I am just looking at the many tabs I have open right now. I would say it is a 50 / 50 % mix. Gmail, Stack overflow, HN are all dynamic. There are a few blogs posts, and tutorials, which are probably mainly static, but get updated on n a regular basis. Newspaper sites, some I am signed into, some I am not.
jgrowl 11y ago
Isn't this how IPFS works? Content is hashed so it will check to see if you have it locally first, then inside your network, then externally from the the closest node that has the data.

by wang_li 11y ago

onion2k 11y ago

How is this distributed model going to deal with the fact that a lot of (all of?) the websites we visit have dynamic content? Web content is rarely very dynamic. With the exception of social networks and news sites, most websites would be largely indistinguishable from what they look like now if they were serving the same page as yesterday or a week ago. Technologically we could trade the 'rendered on request' model with the very latest data for a 'rendered and then cached across the internet for a day' distributed model very easily. Psychologically however, no one would agree to it. People believe their content has to be available to everyone the instant they press Publish.

mrsharpoblunto 11y ago
I disagree - aside from blog sites or marketing/portfolio type sites basically every web application on the modern internet requires per-user dynamic content to function - e-commerce, banking, productivity apps, social networks, messaging etc. the modern web is all about displaying and processing users data. Really any distributed cache is only going to be useful as a replacement for existing CDN's serving static assets (and thats totally fine - it would be great to see the democratization of the performance & scalability of a global CDN)
collyw 11y ago
I am just looking at the many tabs I have open right now. I would say it is a 50 / 50 % mix. Gmail, Stack overflow, HN are all dynamic. There are a few blogs posts, and tutorials, which are probably mainly static, but get updated on n a regular basis. Newspaper sites, some I am signed into, some I am not.

jgrowl 11y ago

Isn't this how IPFS works? Content is hashed so it will check to see if you have it locally first, then inside your network, then externally from the the closest node that has the data.