-
Notifications
You must be signed in to change notification settings - Fork 417
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
Document how to connect browser nodes with Kubo nodes using WebTransport #1286
Comments
At what stage is the JS side of the implementation? Is there a related issue for js-libp2p or js-ipfs? |
I don't think this can be worked on until we have both JS and GO shipped as opt-in in stable Kubo and JS-IPFS releases, and ipfs-webui bug is fixed. |
When we're ready, a tutorial/example would fit nicely into How-Tos > IPFS in the browser: https://docs.ipfs.tech/how-to/ There isn't any other mention in docs of browser nodes being paired with longer-running nodes. This is an architecture we'd like more developers to understand and perhaps use. |
Hi @BigLep docs teams is triaging issues right now, and I saw your comment on #9724:
Based on this, it looks like this issue is still relevant, but docs can't / shouldn't start on this issue yet? Regarding dates, could you help me determine:
I'll set this to |
@ElPaisano : we can document about WebTransport today. #9724 is about WebRTC which is an additional transport from the browser. I think there is enough information about this today, but there are also demos getting created now for IPFS Thing which will help make this clear. @aschmahmann and @SgtPooki will be able to help here. Lets pick this up after IPFS Thing 2023. |
@TheDiscordian : I know you have done work in and around this space? Is drafting something here, something you'd be interested in starting? I think even getting an outline together that myself and others could contribute towards would help. |
There is an explainer in https://connectivity.libp2p.io/#webtransport that could be reused here, what is missing are code examples. Caveat: I suspect this is soft-blocked until we ship https://github.com/protocol/bifrost-infra/issues/2142 and/or ipfs/kubo#9877 (or we need to introduce TLS cert to remove need for
|
Done Criteria
A user can learn about to enabling connectivity between Chromium browser nodes with other implementations like Kubo with WebTransport.
Why Important
We're unlocking great functionality here, but we need to ensure users can discover it, and know how to get started so the impact can be realized.
Notes
The text was updated successfully, but these errors were encountered: