441–450 of 488 posts
Earlier quoted context omitted.
So it differs in implementation details, not in concept.
If you think that your phone number is equivalent to your home address then yes.
Earlier quoted context omitted.
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
Earlier quoted context omitted.
> agree not all apps need that It's less that "not all apps need that" and more that "openziti can be app-embedded" is actually completely false.
OpenZiti has numerous SDKs. If you are a developer and you can integrate an SDK into your application, it 100% is application-embedded. It is incorrect stating that it can't be app-embedded... (i am a maintainer on the project). Perhaps I just don't understand the response?
Earlier quoted context omitted.
Not affiliated, just a happy dev. Nothing about Iroh usage as operator or end-user entails billable metering of keys, clients, QUIC endpoints, bytes transferred etc and to be honest you could deploy pretty extensive Iroh-based software without ever having a financial relationship with number0.
Correct, they do not meter keys, it's a subscription. There appears to be a free tier followed by paid tiers for increased usage ( https://www.iroh.computer/pricing ). I don't use Iroh so I could be wrong, but the goal is definitely a paid service.
As for anything being a "goal"? They do have dev salaries to pay and they offer managed control planes with SLAs or consultations with the core devs to accomplish that.
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…
Earlier quoted context omitted.
It's not for street cred, it's what makes it usable everywhere: Rust, JavaScript (server or browser), Python, Kotlin, Swift, C. Written in JavaScript or Python means limited use, Kotlin or Swift means it could be tricky outside their main platforms, C means worrying about potential vulnerabilities and core dumps. I.e. "written in Rust" is definitely relevant here.
> C means worrying about potential vulnerabilities and core dumps Rust guarantees no vulnerabilities?
Earlier quoted context omitted.
Is there no annual fee on all IPv4 blocks, or just legacy ones, which I'm assuming means blocks that haven't changed hands in a very long time?
I registered this one back in the early 90's, predating the existence of ARIN. No fees only on legacy ones, assuming one has not signed a registration agreement. I assume, at some point, I will be forced into signing an agreement, but it's worked well so far.
Earlier quoted context omitted.
Do I understand this correctly on a semantic level as "MAC address for the Internet"? (Or, in so many words: an alternative for dynamic DNS without a centralized/hierarchical lookup infrastructure that punches through NATs without all the associated hassle). I.e., the problem is "communicate directly with a node on the Internet by its unique ID". The big question is: what do you solve that Kademlia (BitTorrent) doesn…
this is a VERY good writeup of all problems in the stack chronologically that must have cost you time. Thank you for this!
Took a few hours while I was trying to understand what exactly iroh is doing.
It was good to refresh some things in memory along the way, and learn some too :)
How does Iroh's performance compare to wireguard?
I think we do very well with devices devices with limited bandwidth and changing connections. We are able to saturate a 1 GiB link from a normal desktop PC or good phone, but have some work to do to saturate a 10 GiB link with a single process. We don't have a comparison benchmark, but we are fast enough that we are not the limiting factor for many use cases. In many cases the performance bottleneck is the interface…