4 comments

  • tekacs1 hour ago
    <a href="https:&#x2F;&#x2F;github.com&#x2F;quinn-rs&#x2F;quinn&#x2F;issues&#x2F;224#issuecomment-3842537530" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;quinn-rs&#x2F;quinn&#x2F;issues&#x2F;224#issuecomment-38...</a><p>It&#x27;s lovely to see the polite and respectful back and forth in this comment thread where the Iroh folks are talking about deciding to fork. :)
    • bigfishrunning49 minutes ago
      I very much agree, a nice contrast to so much open source drama
      • b_fiive41 minutes ago
        disclosure: I work on the team behind noq. Can&#x27;t emphasize enough that the quinn maintainers are really lovely people, and quinn is an excellent project.
  • agg2313 minutes ago
    iroh seems like a very well positioned product in the era of people rapidly building applications for personal use. I&#x27;m really interested in seeing how they continue to grow.<p>I personally have been looking off and on at providing an &quot;app relay&quot; using it, where people can get an OSS, self-hostable (if desired), zero config way to remotely access their app&#x2F;data on their network. This would be separate than a &quot;network relay&quot; (a la Tailscale), as this is done selectively as part of the application server and client, requires no knowledge or configuration as the user, and exposes a much smaller surface area.
  • adityamwagh34 minutes ago
    Love the folks from n0. I regularly use their sendme cli for peer to peer file transfer!
  • jeffbee50 minutes ago
    I was just reading the QUIC multipath RFC. Didn&#x27;t it come out literally yesterday? I guess it&#x27;s common to have the implementation foreshadowing the RFC but it&#x27;s jarring to see them back to back like this.
    • b_fiive40 minutes ago
      It&#x27;s been a <i>draft</i> for a long while, and was only recently approved