rklaehn

4 ms·

1.
by rklaehn 1mo ago
They built something amazing and now have a nice exit. The code remains open under a non profit foundation. I don't think it is that bad. If working conditions are too bad people will just quit and work for the foundation.
2.
by rklaehn 1mo ago
If you want to compare iroh with something out of the IPFS world, iroh is basically "what if you build libp2p on multipath QUIC". If you want full ipfs functionality, we have a number of protocols you can combine: blobs https:&#x
3.
by rklaehn 1mo ago
Main author of iroh-blobs here. We realised that there are many more use cases for p2p streams than for blobs, so in the last year we have focused on getting iroh to 1.0, which involved implementing our own multipath QUIC implementation bas
4.
by rklaehn 4mo ago
There is this https://github.com/bittorrent/bittorrent.org/pull/174 We would love this to gain more traction so we can use mainline also for content discovery. But we have to be realistic: mainline moves slow
5.
by rklaehn 4mo ago
There are some technical differences since we build on QUIC, not on wireguard. We think that QUIC offers some advantages for demanding use cases. But everything we do is open source as well. Everything in the core is MIT and Apache2 licen
6.
by rklaehn 4mo ago
We have not implemented this yet, and there are some things to consider. But there is an open standard for load balancing QUIC connections, and we have hooks in our QUIC implementation noq to generate connection ids that should allow us to
7.
by rklaehn 4mo ago
You don't have to use it. But here are some answers: Re-issuing keys is as simple as generating a new Ed25519 keypair. let secret_key = SecretKey::generate(); // takes less than a millisecond Iroh as of now has no fleet man
8.
by rklaehn 4mo ago
This might not be a giant difference in practice. But headscale is a community project. The iroh relay code is by number0 just like iroh itself and lives in the same MIT and Apache2 licensed repository. You can even embed it into your webse
9.
by rklaehn 4mo ago
We do have browser support, but as of now it is relay only.
10.
by rklaehn 4mo ago
We have made some progress reducing the set of patches that is needed to get iroh to run on an esp32 with SPIRAM. We just need a little dependency reduction for it to fit, but other than that iroh 1.0 works out of the box now.
11.
by rklaehn 4mo ago
You only need to know the public key of the target endpoint. It will work even on very restrictive firewalls. Even if they outright ban UDP packets, we will fall back to the relay connection which is https/websocket. Note that here is
12.
by rklaehn 4mo ago
That’s the beauty of it. The app end user doesn’t have to do anything. The iroh endpoint will determine its location in the world by probing the configured relays using QAD (similar to STUN). It will then choose a home relay and establish a
13.
by rklaehn 4mo ago
> I might have assumed io_uring would be the high throughput kernel interface for Linux. We might do an io_uring based linux only implementation at some point. For now we do care about performance very much, but also want to have a singl
14.
by rklaehn 4mo ago
Yeah, that’s from a friend of mine. If something like this would gain traction that would be cool.
15.
by rklaehn 4mo ago
It might be an option to provide a good migration path for projects that build on libp2p. But in the long term you probably don't want two fully featured p2p networking stacks in your dependencies.
16.
by rklaehn 4mo ago
Yes, exactly. Basically we chose the bottom edge of zooko's triangle. https://en.wikipedia.org/wiki/Zooko%27s_triangle A mapping from a scarce but human readable name to a non-scarce but not human readable name wo
17.
by rklaehn 4mo ago
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 proc
18.
by rklaehn 4mo ago
That is correct. Iroh connections are at L6, individual protocols such as blobs or gossip are at L7. From the OSI point of view, QUIC itself is a bit of a layering violation. It covers transport (L4, Reliable ordered delivery, stream multip
19.
by rklaehn 4mo ago
Previous similar attempts were often not pragmatic or frugal enough. They cared about peer to peer purity more than about it working under all circumstances. They also frequently overabstracted things. So we got into the sad situation that
20.
by rklaehn 4mo ago
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 a
21.
by rklaehn 4mo ago
I love mainline and also really appreciate how lightweight it is by just using UDP packets. But UDP packets have their limits. With the maximum MTU you can expect to work, the payload can't be more than about 1000 bytes, which is the l
22.
by rklaehn 4mo ago
We don't have the post 1.0 roadmap very fleshed out at this point. The team has been extremely focused on getting 1.0 out of the door for the last year. This took longer than expected, as expected :-) But I can say that some form of gl
23.
by rklaehn 4mo ago
If they are both behind the same CGNat, you can use mDNS to help them find each other. If they are behind different CGNat, you need a party that is reachable by both to help with hole punching and/or relay traffic. This is fundamental,
24.
by rklaehn 4mo ago
We have some customers that do use iroh inside data centers. You get the simplicity of being able to freely move nodes within the data center or even across data centers without having to reconfigure ip addresses. And once a connection is e
25.
by rklaehn 4mo ago
At the lowest level it is a creative way to leverage all the work the major cloud vendors have poured into QUIC for p2p connections. If you look at an iroh connection in wireshark it is just a QUIC connection. If you configure a SSLKEYLOGFI
26.
by rklaehn 4mo ago
Very cool project. I seriously wish one of the printer vendors would use iroh to come up with a network printing standard that just works. We constantly have issues with our printer. I have fewer issues with my bambu 3d printer than with
27.
by rklaehn 4mo ago
Iroh endpoint ids are just Ed25519 keypairs. We don't want you to charge per id, and even if we wanted there is no way we could. We charge you for hosted relays and additional insights into your deployment, but the core is and will alw
28.
by rklaehn 4mo ago
Yes, exactly. Our commercial offering provides more insight into your iroh deployment as well as a hosted relay network. At the enterprise tier you can also get priority access to our engineering team. Obviously we want to make people aware
29.
by rklaehn 4mo ago
DynDNS does not work for devices behind a NAT unless you manually set up port forwarding. Iroh gives you the connectivity of DynDNS without any manual configuration.
30.
by rklaehn 4mo ago
We did have golang bindings in the past, but had to pause all bindings because keeping them up to date was not viable. Now that we have a stable API, we will revisit this. If there is enough serious demand we could publish go bindings. Iroh

More ›