4 ms·

https://veilid.com/ https://veilid.com/ should also be a great alternative. i haven't had time to use it yet, but it was built to address performance issues wit

https://veilid.com/ https://veilid.com/ should also be a great alternative. i haven't had time to use it yet, but it was built to address performance issues with ipfs and allow for both dht style content discovery, but also for direct websocket connections for streaming (and doing that in an anonymous fashion)

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 different. But I would love to get more details.
- ramrunner0xff 3y ago
  https://yewtu.be/watch?v=Kb1lKscAMDQ https://yewtu.be/watch?v=Kb1lKscAMDQ this was the presentation at DC'31. i will also check out iroh! thanks for working in building something in this space, it is much much needed!
  - 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 protocol from tailscale. I am confident that we have a better story regarding handling of large blobs. We don't just use blake3, but blake3 verified streaming to allow for range requests. Also I wrote my own rust library for blake3 verified streaming that reduces the overhead of the verification data. https://crates.io/crates/bao-tree https://crates.io/crates/bao-tree I tried to get on their discord at https://veilid.com/discord https://veilid.com/discord, but I get an invalid invite. You know a better way to get in touch?
    - ramrunner0xff 3y ago
      hmm this is strange, i tried the invite and it worked for me. If you are on fedi, @thegibson@hackers.town is part of the team. thanks for the links, i will get in touch personally when i try ir0h :)

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 different. But I would love to get more details.

ramrunner0xff 3y ago
https://yewtu.be/watch?v=Kb1lKscAMDQ https://yewtu.be/watch?v=Kb1lKscAMDQ this was the presentation at DC'31. i will also check out iroh! thanks for working in building something in this space, it is much much needed!
- 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 protocol from tailscale. I am confident that we have a better story regarding handling of large blobs. We don't just use blake3, but blake3 verified streaming to allow for range requests. Also I wrote my own rust library for blake3 verified streaming that reduces the overhead of the verification data. https://crates.io/crates/bao-tree https://crates.io/crates/bao-tree I tried to get on their discord at https://veilid.com/discord https://veilid.com/discord, but I get an invalid invite. You know a better way to get in touch?
  - ramrunner0xff 3y ago
    hmm this is strange, i tried the invite and it worked for me. If you are on fedi, @thegibson@hackers.town is part of the team. thanks for the links, i will get in touch personally when i try ir0h :)