We want to break the current situation that by default, all wormhole connections go thru a single server.
This is hard to do correctly, since if our code randomly choosing one of N servers every time the app starts, a single wormhole will see most of the IP's on the network over time. We need a smarter algorithm than that.
Our solution will require having a decent sized pool of servers, maybe 10, and randomly choosing 3 of those and then having those be "sticky" for a certain amount of time, and the client only chooses other wormholes if one of those 3 is down. When the "sticky" timeout is up, the node should then choose new random wormholes.
We want to break the current situation that by default, all wormhole connections go thru a single server.
This is hard to do correctly, since if our code randomly choosing one of N servers every time the app starts, a single wormhole will see most of the IP's on the network over time. We need a smarter algorithm than that.
Our solution will require having a decent sized pool of servers, maybe 10, and randomly choosing 3 of those and then having those be "sticky" for a certain amount of time, and the client only chooses other wormholes if one of those 3 is down. When the "sticky" timeout is up, the node should then choose new random wormholes.
1000 HUSH for a good implementation of this