I'm thinking of adding an optional method to deploy a website alongside the ipfs/service-worker-gateway project. Allowing users without IPFS to receive the website with helia in the background and effectively running an in browser true IPFS deployment of an application.
But if I did this. I think I'd want it to work kind of like Blazor Servers auto render mode. AKA signalR first, then WebAssembly after.
AKA, render via centralized while it's loading with IPFS in the background and then able to load with IPFS later once found and cached. This keeps things fast, and decentralized after first render.
I'm thinking of adding an optional method to deploy a website alongside the ipfs/service-worker-gateway project. Allowing users without IPFS to receive the website with helia in the background and effectively running an in browser true IPFS deployment of an application.
But if I did this. I think I'd want it to work kind of like Blazor Servers auto render mode. AKA signalR first, then WebAssembly after.
AKA, render via centralized while it's loading with IPFS in the background and then able to load with IPFS later once found and cached. This keeps things fast, and decentralized after first render.