4 ms·
> All the static content stored with the site still loads, and my modern browser still renders the page (HTML, unlike HTTP, has excellent lasting power). But an
by dleslie 5y ago
> All the static content stored with the site still loads, and my modern browser still renders the page (HTML, unlike HTTP, has excellent lasting power). But any links offsite or to dynamically served content are dead. For every weird example like this, there are countless examples of incredibly useful content that have also long since vanished.
Perhaps I missed it, but I don't see where they claim that IPFS can provide a solution for dynamic content; which makes up a huge portion of what is served over HTTP.
- alvarlagerlof 5y agoIt won't, but much of the web could work well on JAMStack, and there's no reason that couldn't be supported.
- dleslie 5y agoJAMStack isn't much of an option for services that can't trust the clients and cannot rely on high latency consensus algorithms. It's also brutal for battery life.
- oefrha 5y agoJAMStack != static site served entirely by a CDN. There’s an A for API in there. Where’s the A for IPFS? There’s no such thing.
- encryptluks2 5y agoIt can be built, but I don't think there are any frameworks that make it easy. A JSON file can be an API, but authentication and encryption using static publicly available files is more challenging, especially for a large number of users. That is where blockchain solutions come into place.