Yes, it’s. Just not allowed to mimic nodes from the same physical location like they operated in another (circumventing the /24 filter, which is not allowed).
Exactly. This is the main reason for this filter in place. I can believe, that you have a redundancy for everything, but any local disaster still could shutdown your server(s).
Yes. And we are moving to there. We implemented recently the choice of n in the node selection
It would prefer the nodes with a better success rate from otherwise equal nodes. So, basically it would select nodes with a greater latency less often, reducing the probability to select nodes to store the piece of the same segment in the same location, when one or all of them circumventing the /24 filter but increasing a latency doing so.
It’s not 100% solution, but better than only /24 filter.
There is a discussion, how we may improve things even better: