@utunga3 yes it's definitely a case of not-getting-around-to-it-yet.
There is ssb-tunnel which works but isn't actually hole punching... but it's a step towards it.

On a related note, the #sunrise-choir #rust implementation will probably benefit from all the NAT traversal hard-work put into the crust p2p library by the #safe-network folks.

cc: @dinoƧ𝔸Ⓤᖇ @Matt McKegg @Piet @seanb

@E7CH4P0 The equivalent of a BIP has been proposed and is possibly being worked on =P

@ktorn thanks for sharing about crust, I hadn't heard of it, and it could be really useful in our work on Holochain, which is written in Rust as well

I really like the way you framed and surfaced this original inquiry @utunga3 ❀

As demonstrated by crust, this NAT traversal and hole-punching thing actually is a great point to coordinate on, not just within the SSB project, but if it can be a collaboration between parties, and developed in a modular way that can be repurposed across the many types of p2p tools and protocols that we may wish to see proliferate over the coming years

In my work on Holochain, we've currently got a networking library being prototyped in nodejs, but there's no such good solution available. There is a libp2p library, but the JS implementation is missing any NAT traversal capacities.

See the 'NAT traversal' link on this page: https://libp2p.io/implementations/ It was written only into the GO implementation

That is probably why Paul Frazee started setting out to do development of hyperswarm