rklaehn

8 ms·

91.
by rklaehn 2y ago
We use pkarr at iroh.computer for node discovery. It is anything but slow. It is very rare for a lookup to take more than a few milliseconds. It is sometimes faster than our non-p2p node discovery option which is using DNS. DHTs get a bad r
92.
The Did DHT Method Specification 1.0(did-dht.com)
3 points by rklaehn 3y ago|2 comments
93.
Public-Key Addressable Resource Records(github.com)
6 points by rklaehn 3y ago|2 comments
94.
by rklaehn 3y ago
The simplest possible integration between DNS and peer-to-peer overlay networks
95.
by rklaehn 3y ago
That is not a problem specific to IPNS though. Using a DHT for something like IPNS is fine. Publishing roots of large data sets is also fine(ish). Using it to publish every tiny chunk of a large file is a horrible idea. It leads to overwhel
96.
by rklaehn 3y ago
Not yet. We have been busy with other stuff, also the willow spec has been a bit of a moving target until now. We would like to take our rust willow impl and separate it a bit more from our code base, so that iroh documents are just users o
97.
by rklaehn 3y ago
Thanks for letting us know. We will add a section about encryption. These tiny tools are basically one week projects to show off the tech, but they try to be useful on it's own as well.
98.
by rklaehn 3y ago
Difficult to answer. IPNS uses the IPFS kademlia DHT, which has some performance problems that you can argue are fundamental. For solving a similar problem with iroh, we would use the bittorrent mainline DHT, which is the largest DHT in exi
99.
by rklaehn 3y ago
So, I am not the one that is doing the bindings, so take this with a grain of salt. It seems uniffi does create C compatible bindings in order to make bindings for all these other languages. But these are internal bindings that are ugly and
100.
by rklaehn 3y ago
It's using the same transport. Basically sendme is like dumbpipe, but adds blake3 verified streaming from the iroh-bytes crate for content-addressed data transport.
101.
by rklaehn 3y ago
To be fair, IPFS does offer not just content addressing but also a mechanism for mutability with IPNS. You can think of a willow namespace (or iroh document) as a key value store of IPNS entries. The problem with IPNS is that the performanc
102.
by rklaehn 3y ago
Thanks. This is awesome. I think they are doing more work themselves in terms of crypto, whereas we rely on QUIC+TLS more. Regarding holepunching, our approach is a bit less pure p2p, but has quite good success rates. We copy the DERP proto
103.
by rklaehn 3y ago
This looks very interesting. They made very similar choices than we (iroh) did. Rust, ed keys, blake3. They seem to do their own streams, while we are adapting QUIC to a more p2p approach. Also the holepunching approach seems to be differen
104.
by rklaehn 3y ago
It's more generic than that. Syncthing is designed specifically for file system sync (and does a very good job). Willow could be used for file system tasks, but also for storing app data that is unrelated to file systems, like a KV sto
105.
by rklaehn 3y ago
This is a good question. But it is worth noting that not everything has to scale globally. E.g. in iroh-sync (which is an experimental impl of the willow protocol) you are not concerned with global scaling. You care only about nodes that
106.
by rklaehn 3y ago
Prefix pruning is a very different approach than tombstones. An update will actually remove data, and not just mark the data as removed. Maybe "total erasure of data" is a too strong promise, but the fact that you can not force no
107.
by rklaehn 3y ago
Not officially. We currently have bindings for rust, python, golang and swift. These were the most asked for bindings (python for ml, golang for networking and swift for ios apps). We are using uniffi https://mozilla.github.io&#x
108.
by rklaehn 3y ago
Think of it like const generics in languages like rust or C++. You can make two data structures with a const parameter. If the parameter is not the same, they are not compatible (not the same type). The parameter can be tuned according to t
109.
by rklaehn 3y ago
I was not aware of iRODS. Iroh is named by a certain fictional character that likes tea. Any similarity is a coincidence. But it seems like iRODS is much more high level than iroh. E.g. iroh certainly does not contain anything for workflow
110.
by rklaehn 3y ago
if you are looking for something similar to ipfs but a bit more minimalistic and performance oriented, check out iroh https://github.com/n0-computer/iroh . It is a set of open source libraries for peer to peer networki
111.
by rklaehn 3y ago
iroh developer here. willow was not developed in a vacuum. the willow folks have worked with us while we have implemented many ideas from willow, starting with range based set reconciliation ( https://arxiv.org/abs/2212
112.
by rklaehn 3y ago
Yes, this is very true. If you listen to some people you would think that once you have kids your life is basically over. You will never be able to spend any time on yourself anymore. This is just not true - at least if you refuse to become
113.
by rklaehn 3y ago
> Your comment has the whiff of Magical Tech thinking to it. Well, your post has the whiff of malthusian doomerism to it. Look up the Simon-Ehrlich wager. Ehrlich was wrong in every single respect. There are more people, yet they are eco
114.
by rklaehn 3y ago
For every single decade in the 20th century there was some kind of doom hanging over our head. Imagine deciding to have kids in the 80s where the two superpowers were pointing insane amounts of nuclear weapons at each oter. Or in the 70s wh
115.
by rklaehn 3y ago
Why? There are huge stretches of the world that are basically uninhabited. Even in densely populated places like Europe there are large areas with low population density. People are crowding in cities and then complaining that there are too
116.
by rklaehn 3y ago
What's surprising about people having less kids if the prevailing ideology in the west since many decades is basically malthusianism? People are getting told from an early age that humans are a pest and that the world would be better o
117.
by rklaehn 3y ago
Which panics if you don't call it in the right context. So now you have code which can only be used under certain circumstances and with one particular async runtime. Since when has it become acceptable in rust to have fns that just pa
118.
by rklaehn 3y ago
You don't get weird higher-ranked lifetime errors when you use non Sync futures with hand-rolled async traits. I am not saying that this is the reason to use local futures. But if you have decided that local futures are the way to go a
119.
by rklaehn 3y ago
Automatic memory management is not exclusively positive, even if you don't care about performance. If you lose deterministic destructors and therefore the possibility of RAII, for me it is a loss. I worked with lots of garbage collecte
120.
by rklaehn 3y ago
Kind of agree. The erlang runtime just gives you a process abstraction that is extremely cheap. So within a process you can do things logically sequentially without dragging the system as a whole down. This approach would not have been the

More ›