Iroh 1.0
251–260 of 488 posts
Re: Iroh 1.0
#252> Dial keys Maybe it's in the video I didn't watch, but I really think paragraph one should make clear what kind of keys and why. Cryptographic? Asymmetric? How do they do the job, at even the most basic level? It never explains, just dives into abstract claims of superiority and usage stats. I gather relays are involved; this would be a good thing to mention right away instead of making me sift it from the HN discus…
I saw the video and still have no idea what they are. Also, “never locked in” but then “pricing” and why is one paying for “apps” but self hosting relays?
Re: Iroh 1.0
#253I am confused why this is needed. > IP addresses can break, without warning, and it's outside of your device's control. We have DNS? > Keys, however, are created & controlled by you. They stay the same as your device moves, and are yours to throw away, or not. So are domain names? This page does not do a good job of helping me find what it is that I'm missing.
Your phone and laptop don't have stable IPs, let alone DNS entries pointing to them.
Re: Iroh 1.0
#254Huge congrats on the release! I'm slowly trying to build an app on Iroh; it's progressing tiny bit by tiny bit, but I must admit I'm struggling a lot all the time, both with various low-level details, as well as with understanding many high-level aspects, concepts, and approaches. Oftentimes I have to resort to some LLM-generated "wiki" websites to help me progress. I really hope you'll manage one day to allocate som…
We started as an IPFS implementation, but since then the scope of iroh has been reduced. Iroh is not IPFS, but more like libp2p. If you want something like a globally distributed internet archive you would have to use protocols on top of iroh. For example iroh-blobs provides verified streaming of content-addressed data using the BLAKE3 tree hash function. It is very close to itself being 1.0 (probably Q3), but for no…
Sorry if this has been answered or covered on the web I'm currently travelling.
Edit: I managed to read the linked page, thank you for working on such an amazing project!
Re: Iroh 1.0
#255If 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 need Tailscale accounts, and your app is dependent on Tailscale.
Iroh lets you embed this functionality directly, and provides public fallback relays. If your app gets too big for the public relays, using your own relays is the flip of a switch.
Re: Iroh 1.0
#256I am confused why this is needed. > IP addresses can break, without warning, and it's outside of your device's control. We have DNS? > Keys, however, are created & controlled by you. They stay the same as your device moves, and are yours to throw away, or not. So are domain names? This page does not do a good job of helping me find what it is that I'm missing.
What you're missing is that they can't charge you for IP's, and someone else already charges you for DNS/domains. They would like to replace your IP's with keys they lookup. It's a cool idea and I would expect that they'll find a market, but I'm not sure this would be a breakthrough product for me
Re: Iroh 1.0
#257Earlier quoted context omitted.
Those are intended to solve the problem at the OS layer, while Iroh (being a library) does it at the application layer.
Like https://tailscale.com/docs/features/tsnet ?
In theory you could run Headscale, but you're really working against Tailscale's intended design at that point, and Iroh was built for this from the ground up, so what is Tailscale buying you?
Re: Iroh 1.0
#258A wonderful chain to link to the CBDC shackle.
Re: Iroh 1.0
#259If 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…
Re: Iroh 1.0
#260Earlier 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/