Earlier quoted context omitted.
I'm not affiliated with Iroh or even using it, but... "IP works just fine". What!? This is _not_ a solved problem
But what is the actual problem?
Iroh 1.0
181–190 of 488 posts
Re: Iroh 1.0
#182However, I'm confused on the open source vs. commercial offerings. How do they differ? How do they work together?
Re: Iroh 1.0
#183Seems like it'll be a hard sell since steam is already so dominant and enterprise is dominated by tailscale... I see the proposal for being able to work with many different networks from different companies at the same time, but it's a pretty rare usecase and nothing some iptables can't solve.
I can see the argument for chat in heavily censored regions of the world, but not sure if there's any advantages that iroh can offer over other solutions.
Market fit will be hard to find, but best of luck.
Re: Iroh 1.0
#184Earlier quoted context omitted.
Is that not what libp2p already offers? Not sure if it has QUIC out of the box, but hole-punching to UDP connectivity and then running QUIC over it isn't that hard.
Libp2p does have quic, at least the rust implementation.
Re: Iroh 1.0
#185This sounds useful, but isn't this the problem that ipv6 is supposed to solve with 128bit addresses? (I'm not really familiar with why IPv6 never really seemed to take off -- does NAT block incoming IPv6 traffic? (I guess that's the other thing -- even though my devices all seem to have IPv6 addresses I can't recall ever using them))
Iroh addresses are (currently Ed25519) keys. They are not scarce, so you can create them on demand and keep them as you move from one network to another.
If IPv6 was everywhere I guess the hole punching feature of iroh would become less important, but the dial by key feature would remain just as important.
Re: Iroh 1.0
#186Re: Iroh 1.0
#187hey, I helped make this :) will try to answer questions where I can
Re: Iroh 1.0
#188I 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
#189I 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…
> Tor https://github.com/n0-computer/iroh-tor-transport you are using a Tor daemon in it. tor has a rust implementation and when used with rust has stream objects etc. an example of how it's used can be found in https://gitlab.torproject.org/tpo/core/oniux
Arguably directly embedding the rust tor implementation would be more useful for the typical iroh user that wants an embeddable library. I just did not get to it yet.
But thanks for the link.
Re: Iroh 1.0
#190Earlier quoted context omitted.
Iroh is QUIC. We are not trying to reinvent the wheel here, just combining existing IETF RFCs in a creative way. Here is a concrete problem we solve. You have one device in your home WLAN behind a NAT. Your other device is in a 4g network, or behind another NAT at work. In most cases we can give you a direct connection between the two devices very quickly via hole punching, so you get the highest possible bandwidth a…
I made a demo showing it work: https://hw-e4592d7e.web.hallway.com/