Last I checked, tinc supported NAT port punching natively.

As far as I’m aware, that works the same as things like tailscale is doing, where you need at least one node that is publicly reachable to facilitate.

Correct. This is not something Wireguard does, which was the original comparison.

tinc: One public node, thousands of private nodes, with NAT punching. That's fine and typical in my experience.

Which is a much smaller requirement than needing extra software on every NATed node.

So yes it is a differentiated thing between wireguard and tinc, as you phrased it in your other comment.

... because its an problem with NAT and not with the protocol.

Yes. I’m replying to a comment thread debating WireGuard vs tinc where someone said that WireGuard couldn’t, as if it was a differentiated thing between them.