-
Notifications
You must be signed in to change notification settings - Fork 163
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
Tracking: WebAssembly support for iroh-net #2799
Comments
Thanks for the blogspot, and about relay servers. Will Ockam be helpful in end to end encryption? Also can I use any relay server to connect, other wise it will lead to centralization (e.g. storing relay server addresses in dht) |
Great blog post, thank you Philipp. Glad to see Phase 3 being WebRTC, as this means self signed certificates for secure connections (something websocket's can't do, so domain-less nodes are stuck at As far as that complexity, you may want to check out str0m if you haven't already. This was being looked at for libp2p but hasn't been implemented yet. Overall I'm glad to see this route being examined. One of the reasons holding me back from using iroh was lack of browser and webrtc support. So yeah, LFG! |
The traffic that's relayed is already encrypted end-to-end, because we're using QUIC :) (Yes, we're compiling a whole QUIC network stack to Wasm and run it in the browser 🙃 ).
Yes, relay servers are identified by URL. As a node, you can decide to use any "home" relay server you want. |
We're working on Wasm support so you can use iroh-net in rust applications in browsers. See also the accompanying blogpost.
Here's some prior issues with requests for this:
This is a non-exhaustive list of things that need to land for Wasm support:
net
feature to allow disablingsocket2
andstd::net::UdpSocket
dependencies quinn-rs/quinn#2037The text was updated successfully, but these errors were encountered: