[0.8.0a2] lower default prio for former backup servers?

[jcfp]

• The new server priority sets the same default value of zero (the highest priority) for all servers, regardless of their former status as a backup server. This will take many users by surprise, quickly junk up bandwidth/€€€ from (block) accounts intended as fallback only. Any way to handle this more gracefully, by making the default priority (at first run of 0.8.x) for any given server depend on whether it was previously configured as a fillserver?
• Somewhat related: in the server config, the option description only says 0 is highest priority; please also mention the upper bound of 100 for lowest prio there.

[sander]

On top of jcfp's statement:

I think a default value higher than 0 (for example: 3) would be better: if you have 4 servers, and all are on 0 (default), making one server the highest prio, would take three changes (change three times '0' to '1').

If the default value would be 3, it only takes one change (changing '3' to '1')

On the other hand: '3' might look strange to some people. So for them '1' could be a better default value.

[shypike]

I'll implement jcfp's suggestion: backup --> prio 10
Most people have very few servers.
I'll also add the 0..100 range to the help text.

[shypike]

Done for Alpha3