Closed RainaBatwing closed 9 years ago
Symmetric NAT and Port Restricted cone NAT could pose a problem - in this case, both sides would need to generate invites an exchange them, in order to start sending packets at each other.
This isn't unprecedented - many web services require you enter a friend's email address or other globally unique identifier in order to send them an invite.
This is actually exactly the goal of the URI draft (and related issue).
The URI is designed to allow a "router" to act as a public/accessible coordinator such that private nodes don't have to reveal their network location directly. They are flexible enough to be generic as a general address that can be published, or a specific one-time-use-only invite token.
I'm going to close this issue so that we can follow-up on any related topics in the URI issue :)
In an effort to do away with seeds.json, I'd like telehash libraries to include functionality to encode the current user's address (ip, port, maybe public key?) in to a compact string representation. This would ideally be presented in something humanly friendly, like the growing standard in p2p networks: base58. Libraries should include functionality to connect to a mesh network using an invite code, instead of hard coded seeds. This provides a few cool effects: