481–488 of 488 posts
Earlier quoted context omitted.
It's primarily an open source library, not a product. I don't understand why HN seems so concerned about nailing down its "value proposition".
Also, this link is to a version announcement. It makes a poor introduction to iroh because it's not one. The "what is iroh" quesition is answered well in the docs: https://docs.iroh.computer/what-is-iroh
Earlier 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…
"This was not a solved problem until now."
If you're new to Iroh, my mental model is roughly "Tailscale at the application layer instead of the network layer". If your question is, "why not just use Tailscale?", look at it from an app developer's perspective. If you want to release an app and have instances of your app be able to easily connect to each other, you could theoretically embeded Tailscale functionality into your app, but then the users of your app…
> If you want to release an app and have instances of your app be able to easily connect to each other, you could theoretically embeded Tailscale functionality into your app, but then the users of your app need Tailscale accounts, and your app is dependent on Tailscale.
Just use Wireguard directly like everyone else.
Earlier quoted context omitted.
Its amazing to me how people can make a great a product. And then completely bury the lead because they are so deep into the guts of the system You explained the value proposition so well. The website just didnt get to the "why?" At all
It's primarily an open source library, not a product. I don't understand why HN seems so concerned about nailing down its "value proposition".
Imagine if had a nail to drive into a peice of wood, but the onky thing youd ever heard about hammers was either how critical they are in building construction, or about their weight balancing and how much grip the handle has. Youd never know that you could swing the hammer to hit the nail and drive it in
Earlier quoted context omitted.
Its amazing to me how people can make a great a product. And then completely bury the lead because they are so deep into the guts of the system You explained the value proposition so well. The website just didnt get to the "why?" At all
Why? Because if you need to serve ads that are being blacklisted by DNS, you need something like this.
Earlier 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…
"This was not a solved problem until now."
Peers _always_ connected directly to transfer files
A third party server kept an index and provided search, it did not forward traffic between peers
https://docs.iroh.computer/concepts/nat-traversal.md
"If NAT traversal fails, iroh automtically falls back to routing traffic through the relay server"
It has not "solved" the hole punching problem any better than anyone in the past
Alas, it does worse than predecessors by adding a non-P2P default (cf. option)
Earlier quoted context omitted.
Is the LLM-tone of this comment intentional? Or is it just how you normally write? Honest question.
It is how I write. This is what happens when one gets 7 college degrees, people accuse you of writing with AI. I've even been accused of rehearsing AI for how I talk; no, that is how I talk.