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.

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

Leveraging ws://localhost provided by local IPFS node #177

Open
lidel opened this issue Jan 27, 2021 · 1 comment
Open

Leveraging ws://localhost provided by local IPFS node #177

lidel opened this issue Jan 27, 2021 · 1 comment
Labels
dif/expert Extensive knowledge (implications, ramifications) required effort/weeks Estimated to take multiple weeks kind/enhancement A net-new feature or an improvement to an existing feature need/analysis Needs further analysis before proceeding need/community-input Needs input from the wider community needs clarification

Comments

@lidel
Copy link
Member

lidel commented Jan 27, 2021

So js-ipfs running on a web page loaded via https:// is able to connect to ws://localhost:port provided by IPFS node running on the same machine as browser – PoC in ipfs/kubo#5251 (comment)

We could enable WS transport in IPFS Desktop / Brave, but not sure how to leverage it in js-ipfs. This feels related to some prior discussions in ipfs/js-ipfs#3022 and work made by @Gozala, but is also bit brittle (eg. localhost WS dials can be blocked for security reasons)

Open questions:

  • How useful this is today? Perhaps should we park this until IPFS nodes can rebroadcast WANT messages, we have a concept of superodes, or delegated downloads
  • Could localhost WS be added to bootstrap list? How would it work without knowing PeerID upfront? (this is not a /dnsaddr that we can resolve)
@lidel lidel added kind/enhancement A net-new feature or an improvement to an existing feature needs clarification dif/expert Extensive knowledge (implications, ramifications) required need/analysis Needs further analysis before proceeding need/community-input Needs input from the wider community effort/weeks Estimated to take multiple weeks labels Jan 27, 2021
@lidel
Copy link
Member Author

lidel commented Aug 10, 2022

WebTransport (libp2p/specs#404) could provide an interesting alternative here, but TBD if browser vendors will allow using it in localhost / LAN contexts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dif/expert Extensive knowledge (implications, ramifications) required effort/weeks Estimated to take multiple weeks kind/enhancement A net-new feature or an improvement to an existing feature need/analysis Needs further analysis before proceeding need/community-input Needs input from the wider community needs clarification
Projects
None yet
Development

No branches or pull requests

1 participant