-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Epic] Helia Node Type #1284
Comments
Are there any issue about this feature? I would like to use embeded node type directly in chrome browser |
Yes! Some prerequisite work is happening in upstream projects:
Mid term (technically possible)Once we have SW Gateway implementation that works reliably, Initially, it will be deployed on some domain name, to provide origin isolation benefits of subdomain gateway. This will provide drop-in replacement for deserializing subdomain gateways like https://dweb.link, but running gateway will be inexpensive, as it does not act as conduit in data transfer (behind the scenes blocks will be fetched from multiple providers, and hash verification will happen on users machine). Long term (needs new APIs in browsers)Our hope is that at some point in the future browser's will allow extensions to register SW as protocol handler: When that happens, ipfs-companion alone will be able to provide a experience to |
js-ipfs (embedded) node type was removed in #1225, helia can be a viable replacement. Consider helia as a node type.
The text was updated successfully, but these errors were encountered: