381–390 of 488 posts
Earlier quoted context omitted.
Libp2p does have quic, at least the rust implementation.
would it possible to have iroh as a libp2p pluggable transport? So you could dial a iroh node with /iroh/proxy/ed25519key?
But in the long term you probably don't want two fully featured p2p networking stacks in your dependencies.
Are there any good end-user apps that are supported on a broad set of platforms and use Iroh to support file transfers between e.g. Windows and iOS seamlessly?
We wrote a small demo app called sendme to show off iroh. It is cli only, works on all operating systems that we use internally, and we frequently use it to send around qlog files: https://www.iroh.computer/sendme There are several projects inspired by sendme that use the same protocol but add mobile device support and a GUI: https://www.altsendme.com/en https://github.com/ARK-Builders/Drop-Desktop https://github.com…
Earlier quoted context omitted.
The doc still doesn't show what such a 'key' looks like? Why can't there be a simple infographic that goes like 127.0.0.1 -> 'key'
It seems to use DHT under the hood whether directly or through a relay. https://pkdns.net/ .
Earlier quoted context omitted.
vpns typically add at least one hop. this has the possibility of connecting directly via hole punching
Cisco Dynamic Multipoint VPN will start by connecting to a central VPN server and then learn the public IPs of endpoints and automatically create VPN tunnels to them. It can scale to thousands of endpoints.
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…
That explanation still seems overly complicated. Iroh isn't a VPN. Iroh just lets apps connect to each other, just like plain old TCP, but without the shackles of NAT, DNS and dynamic IP addresses that made that impossible. It's restoring simple P2P connectivity to the Internet.
Earlier quoted context omitted.
Exactly. We use DNS TXT records for our default address lookup system. But we also support fully p2p address lookup via the mainline DHT. And if you have another suitable system, you can also plug it in. E.g. you might want to use another DHT that allows mapping from a key to some address data.
Won't relay based networking if adopted at scale enable better censorship and taking like phone networks?
With the relay daemon being self-hostable and OSS any use-case that needs to be more censorship-resistant than that has the option to run their own relays as needed.
A relevant free and open source competitor: https://github.com/EasyTier/Easytier
The site mentions preferring open standards in the IETF - where is it being discussed there?
The site mentions preferring open standards in the IETF - where is it being discussed there?
I 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
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.