Iroh uses noq to establish QUIC connections between endpoints. (github.com)
from cm0002@europe.pub to programming@programming.dev on 15 Jun 18:10
https://europe.pub/post/13250298

#programming

threaded - newest

noxypaws@pawb.social on 15 Jun 21:12 next collapse

utterly useless headline to anyone who doesn’t know what those things are (me)

yetAnotherUser@lemmy.ca on 15 Jun 23:45 next collapse

Would you mind explaining what those things are?

noxypaws@pawb.social on 16 Jun 01:37 collapse

I don’t know what they are.

yetAnotherUser@lemmy.ca on 16 Jun 10:41 collapse

Oops, I misread your comment 💀

JakenVeina@midwest.social on 16 Jun 02:02 next collapse

Par for the course in much of the software industry. It infuriates me, as well.

eager_eagle@lemmy.world on 16 Jun 02:18 next collapse

IP addresses change or can be unreachable (e.g. requiring NAT traversal), so this tool lets you connect two machines (P2P) using a collection of other tools and protocols like relay servers, noq, and gossip protocol. Communication is based on QUIC, the same protocol supporting HTTP/3.

ISO@lemmy.zip on 16 Jun 02:19 next collapse

The real news is that iroh hit v1.0.0.

noq is a fork of crate that implements QUIC which iroh uses. In other words, it’s a minute implementation detail not immediately relevant at all to people who don’t even know what iroh is (yet).

How did we get here? OP text is copied verbatim from the README, with the presumption that it’s relevant, but it isn’t.

How did that happen? I would assume no human was directly involved in doing that, which would be par for the course with that shit-reposting account.

brian@programming.dev on 16 Jun 13:45 collapse

I think we get some leaking from hackernews. when a project gets big there, people just post links here without the original context.

news.ycombinator.com/item?id=48542480

brian@programming.dev on 16 Jun 13:43 collapse

for anyone that it helps: picture tailscale at the app level without having to be in the same tailnet first