Adding a non-HTTP protocol is a major change to the web, and also to every aspect of how browsers are designed and implemented. Steep hill to climb. That said, here are some things that may be useful in your quest: - I spent a couple of years on a retrieval-only approach for integrating IPFS into Chromium, that perhaps can be useful input for that direction. There's code, learnings and context in this and the linked posts there: https://littlebearlabs.io/perspectives/ipfs-chromium-updates. - IPFS+Libp2p is a *lot*... however, its history is a long slow decomposition into smaller parts. The most recent is splitting out *addressing* into a minimal subset of sane defaults, which are compatible with HTTP addressing. This might be a good starting point for retrieval-only approach. More at https://dasl.ing/rasl.html - The approach towards HTTP integration has changed a lot in the IPFS world, so it's worth getting very familiar to where that thinking is at. For example, the Interplanetary Shipyard team has focused a lot on approaches like the ServiceWorker gateway: https://github.com/ipfs/service-worker-gateway
Bug 1354807 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Adding a non-HTTP protocol is a major change to the web, and also to every aspect of how browsers are designed and implemented. Steep hill to climb. That said, here are some things that may be useful in your quest: - I spent a couple of years on a retrieval-only approach for integrating IPFS into Chromium, that perhaps can be useful input for that direction. There's code, learnings and context in this and the linked posts there: https://littlebearlabs.io/perspectives/ipfs-chromium-updates. - IPFS+Libp2p is a *lot*... however, its history is a long slow decomposition into smaller parts. The most recent is splitting out *addressing* into a minimal subset of sane defaults, which are compatible with HTTP addressing. This might be a good starting point for retrieval-only approach. More at https://dasl.ing/rasl.html - The approach towards HTTP integration has changed a lot in the IPFS world, so it's worth getting very familiar to where that thinking is at. For example, the Interplanetary Shipyard team has focused a lot on approaches like the ServiceWorker gateway: https://github.com/ipfs/service-worker-gateway - The HTTP Gateway and Exchange sections of the IPFS specs are highly relevant: https://specs.ipfs.tech/