4 ms·
So iroh is basically WebRTC, except it works in and outside of a browser. Relays seems quite similar to TURN/STUN servers except they also handle fallback traff
by opem 4mo ago
So iroh is basically WebRTC, except it works in and outside of a browser. Relays seems quite similar to TURN/STUN servers except they also handle fallback traffic much like TOR guard/relay nodes
- Sean-Der 4mo agoDoes WebRTC not work inside/outside of the browser anywhere?
- nunobrito 4mo agoIt works outside the browser too, I've been using it that way.
- opem 4mo agoYes 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/ 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.
- syllogistic 4mo agoIt'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 4mo ago> We built & continually check that iroh can compile to WASM & run in the browser
- rklaehn 4mo agoWe do have browser support, but as of now it is relay only.
- syllogistic 4mo agoApologies 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.