I'm out of my technical depth here, but out of curiosity: is this meant to be a full replacement for the current IP address paradigm, or is this meant to be a specific tool on top of/alongside IP addresses that solves particular problems/frictions?
Iroh 1.0
51–60 of 488 posts
Re: Iroh 1.0
#52I don't understand the problem its trying to solve in the first place, IP works just fine, such as DNS. There is already IPv6 and quic, you need vendor and major software to have any traction in that field.
Re: Iroh 1.0
#53I don't understand the problem its trying to solve in the first place, IP works just fine, such as DNS. There is already IPv6 and quic, you need vendor and major software to have any traction in that field.
Re: Iroh 1.0
#54Re: Iroh 1.0
#55I am one of the iroh developers. A question that frequently comes up: when will iroh support webrtc, or BLE, or LoRa, or ... Iroh as of now supports only IPv4, IPv6 and relay transports out of the box. There is such a large variety of potentially interesting transports out there that we can't support all of them without turning the codebase into an unmaintainable maze of feature flags. But we have added the ability t…
Re: Iroh 1.0
#56Re: Iroh 1.0
#57To me this sounds like tailscale - does anyone have any insight into how what this is doing is similar or different?
I love Tailscale, it's deployed on all my devices. But I might check this out for the transports part in particular.
Re: Iroh 1.0
#58To me this sounds like tailscale - does anyone have any insight into how what this is doing is similar or different?
Re: Iroh 1.0
#59LM studio recently released a mobile app powered by Tailscale -- https://lmstudio.ai/link . Iroh seems like a perfect OSS alternative for implementing similar p2p features.
Re: Iroh 1.0
#60Earlier quoted context omitted.
What are the risks if any of running public relays? Is this similar in concept to running Tor Guard Nodes / Relays?
If you run a public unauthenticated relay you act as a home relay for whoever has your relay configured in their relay map and is close in terms of latency. So you might get a lot of traffic. You can configure rate limiting, as we do on our public relays. The traffic is fully encrypted and can not be decrypted by the relay. The only information the relay has is what is necessary for it to function - the endpoint id a…
Nice. I already do rate limiting, traffic balancing using sch cake. This looks like an interesting project. I could envision open source NVR's implementing this. I also like the name of the project.