Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Epic] Helia Node Type #1284

Open
whizzzkid opened this issue Sep 20, 2023 · 2 comments
Open

[Epic] Helia Node Type #1284

whizzzkid opened this issue Sep 20, 2023 · 2 comments
Labels
effort/weeks Estimated to take multiple weeks exp/expert Having worked on the specific codebase is important kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now post-mv3 Tasks to be done after MV3 release

Comments

@whizzzkid
Copy link
Contributor

js-ipfs (embedded) node type was removed in #1225, helia can be a viable replacement. Consider helia as a node type.
@whizzzkid whizzzkid added need/triage Needs initial labeling and prioritization kind/enhancement A net-new feature or improvement to an existing feature exp/expert Having worked on the specific codebase is important P3 Low: Not priority right now post-mv3 Tasks to be done after MV3 release effort/weeks Estimated to take multiple weeks and removed need/triage Needs initial labeling and prioritization labels Sep 20, 2023
@Thaina
Copy link

Thaina commented Apr 5, 2024 •
edited

Are there any issue about this feature? I would like to use embeded node type directly in chrome browser

@lidel
Copy link
Member

lidel commented Apr 12, 2024 •
edited

Yes! Some prerequisite work is happening in upstream projects:

Mid term (technically possible)

Once we have SW Gateway implementation that works reliably,
we will be able to add it as alternative backend here in Companion.

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 ipfs:// backend in Brave.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/weeks Estimated to take multiple weeks exp/expert Having worked on the specific codebase is important kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now post-mv3 Tasks to be done after MV3 release
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Needs Grooming
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lidel @Thaina @whizzzkid