Option to server fallback to next bookmarked server.

[nostitos]

Everytime the server we use goes down for just 1h it causes a disproportionate amount of confusion for the users.

This is a situation where the end user is not the same as the person who's chosen the server,

This invariably lead to them switching to Automatic selection and compromise any privacy gain that was being achieved by using trusted servers.

[SomberNight]

Indeed there could be an option to restrict auto_connect to only connect to bookmarked servers. (ref https://github.com/spesmilo/electrum/pull/8865 )

[SomberNight]

Note: conceptually there are two different options here:

• only restrict history server to bookmarked set, other connected nodes can be any
• restrict all connected nodes to bookmarked set

[ecdsa]

Note: conceptually there are two different options here:

* only restrict history server to bookmarked set, other connected nodes can be any

* restrict all connected nodes to bookmarked set

I think that nuance would be difficult to grasp. However, we could have a single option that:

• restricts history server to bookmarked set
• prioritizes header nodes to be in the bookmark set

So, the behavior regarding extra header nodes would depend on the number of bookmarked servers

[ecdsa]

Actually, I realize we do not need 4 connection modes.

The current "manual selection" and "oneserver" modes could be extended to use bookmarks:

• in the "manual selection" mode, we could select a server from the list of bookmarks. this is similar to auto-connect, but with a restricted set.
• in the "oneserver" mode, we also impose that header nodes are from the list of bookmarks. (of course the 'oneserver' name should be changed)

So, the current situation is simply a case where the set of bookmarks contains one element.