Re: [w3c/ServiceWorker] Remove foreign fetch (#1188)

Very sad to hear that this has been dropped. We, the IPFS Project, were super excited about this feature -- https://github.com/ipfs-shipyard/ipfs-service-worker/issues/5 --

> With double keying, when example.com uses the fonts.google.com foreign worker, it has storage and execution keyed to example.com+fonts.google.com

Making the the base storage to be content address vs kv would enable the browser to avoid false cache misses.

>  and unclear use-cases

Foreign Fetch would enable an IPFS Node to run on a Service Worker and become the ideal Content Addressed CDN.

You can try a taste of this with by visiting https://js.ipfs.io

<img width="1313" alt="image" src="https://user-images.githubusercontent.com/1211152/48691896-81ea2500-ebd4-11e8-8ea9-390ae805b8a2.png">

Once enabled, a js-ipfs node is spawn in a Service Worker and any request to js.ipfs.io/ipfs/SomeHash will be routed through the js-ipfs node itself. With foreign fetch, we would be able to load webpage assets from js.ipfs.io and **if the Service Worker was installed, the browser could cache it or even better, serve it locally to other browsers**, if the Service Worker was not installed, it would it one of the IPFS Gateways.

I believe this to be a fantastic use case for foreign fetch as it would enable Web Assets to be loaded through a DWeb Protocol that verifies their integrity and can serve the same assets fetch to close peers. Would love to have your opinion and know if there is still time to make the case.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1188#issuecomment-439796044