Live data from Hacker News

Viewing profile — rklaehn

rklaehn

HN member
Joined
Mon, Oct 16, 2017, 5:04 PM UTC
HN karma
1,039
Public activity
286 items

About rklaehn

No profile information was provided.

Recent public activity

  1. comment
    Comment #48566574

    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 re…

  2. comment
    Comment #48566562

    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 sourc…

  3. comment
    Comment #48566544

    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 implementa…

  4. comment
    Comment #48566525

    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 …

  5. comment
    Comment #48566434

    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 Apache…

  6. comment
    Comment #48556717

    We do have browser support, but as of now it is relay only.

  7. comment
    Comment #48555471

    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 othe…

  8. comment
    Comment #48555390

    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 …

  9. comment
    Comment #48554379

    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 (simila…

  10. comment
    Comment #48553941

    > 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 a…

  11. comment
    Comment #48553476

    Yeah, that’s from a friend of mine. If something like this would gain traction that would be cool.

  12. comment
    Comment #48552953

    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 y…

  13. comment
    Comment #48552822

    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-scar…

  14. comment
    Comment #48552697

    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 …

  15. comment
    Comment #48552641

    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 co…

  16. comment
    Comment #48552533

    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 o…

  17. comment
    Comment #48552236

    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:…

  18. comment
    Comment #48552145

    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 payl…

  19. comment
    Comment #48552044

    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 expec…

  20. comment
    Comment #48552022

    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 h…

  21. comment
    Comment #48551983

    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 ha…

  22. comment
    Comment #48551807

    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 …

  23. comment
    Comment #48551521

    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 printe…

  24. comment
    Comment #48551428

    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 insi…

  25. comment
    Comment #48551122

    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 …