Listen on two relays instead of one?

[dpc]

Please correct me if I'm wrong but AFAIU an endpoint will detect a single closest relay and then subscribe on it to receive connections. The other day it made me think - isn't that a single point of failure (in a way)? What if a relay has degraded connectivity to a part of the world, or some other mishap that the already subscribed node can't easily detect. Made me wonder - wouldn't one want to e.g. register on two gateways, so clients that fail to connect via one had somewhere else to try.

[flub]

1. The single point of failure is not that bad: the endpoint would re-connect to the next best available relay and start advertising that as it's home relay. That might not be the smoothest right now, but that's bugs in iroh. It should be totally smooth!
2. Yes, we totally want to support having multiple "home" relays! That's one of the reasons of the latest changes to EndpointAddr which can now contain a list of relay servers. Currently that's just one, but you'll be able to have multiple.

[matheus23]

The single point of failure is not that bad: the endpoint would re-connect to the next best available relay and start advertising that as it's home relay. That might not be the smoothest right now, but that's bugs in iroh. It should be totally smooth!

That's not exactly what dpc is referring to here: They're referring to the case where the client that's connected to the relay has perfect connectivity, but another client that wants to connect to that client via the same relay doesn't have connectivity to that relay.

[dpc]

Yeap, we had just a situation like it where we suspected this is actually happening with a user in South America. Turned out not to be the case, but it is not impossible. Could happen even for technical or even political reasons.