You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, the LNL Bridge that Resonite uses is determined by which compatible bridge has the newest "timestamp" value from https://api.resonite.com/networkNodes
Aus, will always be picked over EU, This is because its update cycle(when it reports back to the api), is slightly offset from Aus based on when it was restarted.
Timestamp is therefore not a good measure for the best Bridge, AUS might have the worst network performance but the fastest update and lead to it being picked all the time.
Describe the solution you'd like
I'd like the bridge selection to be based on ping like the Relays
Describe alternatives you've considered
At this point, there's really only one alternative which is that the server which is that each time the nodes are restarted, one node will end up "winning" based on restart time when the Updating loop starts.
Additional Context
No response
Requesters
Me
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the LNL Bridge that Resonite uses is determined by which compatible bridge has the newest "timestamp" value from https://api.resonite.com/networkNodes
For example in this abbreviated api response:
Aus, will always be picked over EU, This is because its update cycle(when it reports back to the api), is slightly offset from Aus based on when it was restarted.
Timestamp is therefore not a good measure for the best Bridge, AUS might have the worst network performance but the fastest update and lead to it being picked all the time.
Describe the solution you'd like
I'd like the bridge selection to be based on ping like the Relays
Describe alternatives you've considered
At this point, there's really only one alternative which is that the server which is that each time the nodes are restarted, one node will end up "winning" based on restart time when the Updating loop starts.
Additional Context
No response
Requesters
Me
The text was updated successfully, but these errors were encountered: