Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Iroh 1.0

iroh.computer

Post reply on HN
Print view View original

321–330 of 488 posts

Re: Iroh 1.0

#321

Post by ben-schaaf »

syllogistic wrote: post #300
opem wrote: post #200

Earlier quoted context omitted.

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

It'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.

> We built & continually check that iroh can compile to WASM & run in the browser

Re: Iroh 1.0

#322

Post by z3ratul163071 »

tootie wrote: post #233
coldblues wrote: post #208

The future of networking is decentralization. I'm a huge fan of Yggdrasil and I2P. We should just be able to buy a mini PC to run 24/7 and host whatever it is that we need on it and seamlessly connect to others. A lot of techies already have older spare machines laying around collecting dust that can become servers. It is far cheaper in the long run and easier to maintain than having to deal with domains and server h…

It's been the future for at least 20 years now.

[dead]

Re: Iroh 1.0

#323

Post by waynesonfire »

apitman wrote: post #255

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…

why isn't your mental model to use DNS?

Re: Iroh 1.0

#324

Post by ramoz »

mckirk wrote: post #276
ramoz wrote: post #154

Ive been prototyping with Iroh for awhile. I think this tech (modern p2p) represents what agent-to-agent (a2a) should be built on. Every agent should be reachable to each other without hosting itself as an http server. related prototypes https://github.com/eqtylab/agentbeam https://github.com/eqtylab/real-a2a

_Every_ agent? I surely hope not. But it would be an interesting... artisocial experiment?

I mean, I didn't mean specifically every agent, and I also did not mean as a experiment. I see real at scale uses for this. Agents operating on their own networks, cross-team agents, my own agents on my own laptop, etc. Sharing context only gets more important the better these things get.

Re: Iroh 1.0

#325

Post by syllogistic »

apitman wrote: post #316
syllogistic wrote: post #298

Earlier quoted context omitted.

> when will iroh support webrtc... This would give you a native iroh node that also speaks webrtc but I find that what folks want is for browsers to participate as peers. I build p2claw, p2p for self-hosted web apps, and ended up doing both halves separately. Box to box is iroh, although I use my own coordinator service and run my own iroh relay. Browser to box is webrtc with a service worker that makes the browser a…

I discovered p2claw the other day and it's really cool. I'm a little surprised you're running Iroh as well. Why not just use WebRTC for everything once you're forced to for the browser anyway?

[dead]

Re: Iroh 1.0

#326

Post by ben-schaaf »

nicebyte wrote: post #253
ben-schaaf wrote: post #143

Earlier quoted context omitted.

Your phone and laptop don't have stable IPs, let alone DNS entries pointing to them.

but dynamic DNS is a thing. I've had setups for it since god knows how long, though admittedly not on my phone.

Dynamic DNS takes setup for every single device, and obviously doesn't work for devices that switch networks frequently. It also doesn't help you if the IP is behind a NAT.

Re: Iroh 1.0

#327

Post by [deleted] »

ben-schaaf wrote: post #320
dotancohen wrote: post #261

Earlier quoted context omitted.

> Dial keys. Not IPs. > It's a simple idea really, and it's the right abstraction for the future of the internet. IP addresses can break, without warning, and it's outside of your device's control. Keys, however, are created & controlled by you. They stay the same as your device moves, and are yours to throw away, or not. IP addresses can be private and inaccessible behind firewalls, but with iroh your device can be…

DNS doesn't work with constantly changing IPs, like you have on mobile networks. DNS also doesn't help when the IP is behind a NAT. So I really don't see how the two are similar at all.

[deleted]

Re: Iroh 1.0

#328

Post by cwillu »

waynesonfire wrote: post #323
apitman wrote: post #255

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…

why isn't your mental model to use DNS?

DNS is piece of the required kit, and not the only hard part of the task.

Re: Iroh 1.0

#329

Post by samrus »

apitman wrote: post #255

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…

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

Re: Iroh 1.0

#330

Post by waynesonfire »

samrus wrote: post #329
apitman wrote: post #255

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…

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.
Post reply on HN