rklaehn

6 ms·

31.
by rklaehn 4mo ago
It isn't meant to be groundbreaking. It is meant to be a rock solid building block that you can put into your application. That being said, I think our use of QUIC multipath is pretty novel. If you use tailscale or a VPN, your connecti
32.
by rklaehn 4mo ago
I work on iroh. On the technical level, the biggest difference is probably that we build on QUIC whereas tailscale builds on wireguard. Iroh is a library that is made to embed into your application, whereas the tailscale offering started as
33.
by rklaehn 4mo ago
We are using QUIC, but using a QUIC/TLS extension called raw public keys in TLS . The DNS is not involved in any way, and there is no way anybody can shut down your usage of iroh. https://datatracker.ietf.org/doc&#x2
34.
by rklaehn 4mo ago
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 ir
35.
by rklaehn 4mo ago
The core is open source and always will be. Crates are licensed the usual for rust: Apache2 and MIT. This also includes the relay servers. In addition we provide services that any commercial deployment using iroh will probably find essentia
36.
by rklaehn 4mo ago
I might be crazy, but I got a side project to write a DHT using iroh. The key is to use QUIC 0-rtt connections to keep the connection overhead minimal. But at this point it is just a toy project to push the limits of what is possible with i
37.
by rklaehn 4mo ago
We do not use DERP. But yes, relay to relay communication is something we want to look into in the future for some use cases. As of now relays are completely self contained and pretty dumb. The protocol does not require relay to relay com
38.
by rklaehn 4mo ago
1. Currently we are using Ed25519 keys. You could use our existing discovery services to add a level of indirection from a root key to the currently active key. It wouldn't be that much code, since the discovery services are pretty gen
39.
by rklaehn 4mo ago
No. The data in each direction is encrypted by TLS, using ephemeral keys. Only the owner of the corresponding private key can initiate a connection from their public key, or receive a connection attempt to their public key. Let's say y
40.
by rklaehn 4mo ago
We think a library is more useful for widespread adoption. I can't get my mother to install a daemon, but I can get her to download an app that uses iroh under the hood. Besides, as a lot of people have mentioned already, if you want a
41.
by rklaehn 4mo ago
Yes, you will get secure direct connections. This matters for privacy in case of an encrypted chat, but also has a lot of benefits for more demanding use cases such as video streaming. Here is a video of frando from our team demoing media o
42.
by rklaehn 4mo ago
Yes, I wrote the current tor transport as a quick demo/testground for custom transports. Arguably directly embedding the rust tor implementation would be more useful for the typical iroh user that wants an embeddable library. I just di
43.
by rklaehn 4mo ago
IPV6 addresses are still addresses. They get assigned to your device, and change as you change networks. Iroh addresses are (currently Ed25519) keys. They are not scarce, so you can create them on demand and keep them as you move from one n
44.
by rklaehn 4mo ago
We should definitely do a better job explaining this. Regarding security, one thing to be aware of is that iroh connections are just standard QUIC connections secured using standard TLS with the (also standard) raw public keys in TLS exten
45.
by rklaehn 4mo ago
We have plenty of very deep technical content on our blog, explaining features of QUIC such as 0-rtt, post-quantum key exchange, address validation tokens, embedded devices. A great thing about iroh is that due to it being just QUIC, when y
46.
by rklaehn 4mo ago
No. IP isn't going anywhere. The intent is to provide additional capabilities on top of IP. That being said, if IP ever gets replaced, your iroh based app will continue to work pretty much unchanged. Iroh will just get you the best pos
47.
by rklaehn 4mo ago
Holepunch, formerly hypercore, formerly dat, is a great project. Their main language is js, which makes it difficult to embed into anything but js/ts applications. Also, they are very principled when it comes to peer to peer purity, wh
48.
by rklaehn 4mo ago
thank you!
49.
by rklaehn 4mo ago
There are already some crates providing a bridge between LoRa using iroh. See for example https://crates.io/crates/donglora-bridge I am not aware of a LoRa custom transport yet, but that is not unexpected given that th
50.
by rklaehn 4mo ago
There is nothing unfree about iroh. All core crates are published with the standard MIT and Apache2 licenses.
51.
by rklaehn 4mo ago
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 D
52.
by rklaehn 4mo ago
libp2p does have QUIC, but it is one of many possible transports. So libp2p builds many things on top of the underlying transport where we use QUIC directly and use existing mechanisms such as TLS ALPNs for protocol negotiation. We also use
53.
by rklaehn 4mo ago
If you are a rust developer, you can just take a look at the examples in the iroh repo itself or in our iroh-examples repo. None of them require an API key. https://github.com/n0-computer/iroh/tree/main/i
54.
by rklaehn 4mo ago
Iroh is just a clever combination of existing standards such as QUIC with some draft RFCs and a tiny bit of clever custom logic added via TLS extensions. So in theory a go implementation is possible using a go QUIC implementation that suppo
55.
by rklaehn 4mo ago
I would say it is an excellent building block for application developers to route around the segmentation. There are several projects that work well in restricted enviroments that use iroh for some features. E.g. https://delta.ch
56.
by rklaehn 4mo ago
I would say it is not a replacement but an addition. IP isn't going anywhere any time soon, but we add two capabilities on top. The ability to dial an endpoint by key, and the ability to get direct connections whenever possible. That b
57.
by rklaehn 4mo ago
First of all: the p2p address lookup is an optional feature. You have to explicitly enable it. Mainline is incredibly frugal in terms of resource use, but we want it disabled by default so mobile apps don't look like bittorrent clients
58.
by rklaehn 4mo ago
Take a look yourself. Our code is as good as we can make it, and everything is modular and well documented. For example our QUIC implementation noq which underlies every iroh connection can also be used as a standalone QUIC impl that implem
59.
by rklaehn 4mo ago
A difference between iroh and many p2p networks is that we try to use existing IETF standards (QUIC, TLS) as much as possible instead of reinventing the wheel. An iroh connection is just a QUIC connection, using TLS and TLS ALPNs for protoc
60.
by rklaehn 4mo ago
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

More ›