So iroh is basically WebRTC, except it works in and outside of a browser. Relays...

syllogistic · 2026-06-16T01:21:19 1781572879

It's backwards! Unlike webrtc, iroh doesn't work inside a browser. It's for the case where you have two native apps that need to talk to each other p2p.

For browser / webapps you want webrtc.

ben-schaaf · 2026-06-16T05:00:15 1781586015

> We built & continually check that iroh can compile to WASM & run in the browser

syllogistic · 2026-06-16T19:38:13 1781638693

Apologies I should have been more precise. What I meant was it doesn't work on the browser support in the way webrtc works on the browser. The point of webrtc on the browser is to establish a peer to peer connection.

rklaehn · 2026-06-16T15:23:51 1781623431

We do have browser support, but as of now it is relay only.

Sean-Der · 2026-06-15T18:59:46 1781549986

Does WebRTC not work inside/outside of the browser anywhere?

nunobrito · 2026-06-15T19:27:51 1781551671

It works outside the browser too, I've been using it that way.

opem · 2026-06-15T19:59:08 1781553548

Yes it does! I was trying to draw an analogy there, I think it would be better to state as - iroh is similar to WebRTC + PeerJS[1] which only works on browsers, generally[2].

[1]: PeerJS(https://peerjs.com/) is a library to use WebRTC w/o any boilerplate code. [2]: WebRTC functionality can be enabled in non-browser envs like Node.js by using third-party native addons (like node-webrtc) that provide bindings to the underlying C++ WebRTC library.