Feature description:
I think it could be helpful to allow any number of alternate connection sources. Currently there is a primary and secondary, but a list that allows for more than two connection sources would be really helpful for my niche use case.
Problem solved:
For a single source, I have more than two possible connection endpoints for my subsonic server. I have a local url, a url that is accessible via VPN, and a third public facing url. In my situation, I am not always home. My public IP can change, breaking the public facing url. I have a backup VPN connection that can be used if the first two are unavailable, but there is no way to add more than two connection sources.
Brought benefits:
This feature would allow users to add more endpoints for their server, which can improve connection reliability as there are more endpoints to fall back onto.
Other application solutions:
Immich has a great solution to this. The connection sources is a list, where each list entry has a potential url. The higher the entry is in the list, the higher priority that connection has. This way, I can prioritize my local url, then the public facing url, then the backup vpn url, and add even more connection sources if needed.
Additional description and context:
Screenshots / Mockup: