The SDL source code can now list at least 3 "stable"-ish SDL servers, which can be rotated around in requests.
If one server is down, it should try another server without bothering the user. Only if all servers are down should the user see a GUI error/warning.
The goal here is to have many community-run servers and for at least one of them to be operational and non-malicious at any given time. A boy can dream.
Our design plans for malicious servers, and SDL clients will rotate their requests to whatever SDL servers that are up, instead of getting "stuck" on one malicious SDL server.
NOTE: Users with high privacy requirements SHOULD NOT USE COMMUNITY SERVERS and instead run their own SDL server. That is the only way to assure privacy at the same level as using a full node.
The SDL source code can now list at least 3 "stable"-ish SDL servers, which can be rotated around in requests.
If one server is down, it should try another server without bothering the user. Only if all servers are down should the user see a GUI error/warning.
The goal here is to have many community-run servers and for at least one of them to be operational and non-malicious at any given time. A boy can dream.
Our design plans for malicious servers, and SDL clients will rotate their requests to whatever SDL servers that are up, instead of getting "stuck" on one malicious SDL server.
NOTE: Users with high privacy requirements SHOULD NOT USE COMMUNITY SERVERS and instead run their own SDL server. That is the only way to assure privacy at the same level as using a full node.
@onryo@jahway603 you added your servers to the static list of "Default servers" a user can choose, but that just let's users choose a single static server for all requests. If it's down, SDL doesn't work. This issue is important to do for the 1.4.1 release, so we rotate around our API requests to different servers
@onryo @jahway603 you added your servers to the static list of "Default servers" a user can choose, but that just let's users choose a single static server for all requests. If it's down, SDL doesn't work. This issue is important to do for the 1.4.1 release, so we rotate around our API requests to different servers
The SDL source code can now list at least 3 "stable"-ish SDL servers, which can be rotated around in requests.
If one server is down, it should try another server without bothering the user. Only if all servers are down should the user see a GUI error/warning.
The goal here is to have many community-run servers and for at least one of them to be operational and non-malicious at any given time. A boy can dream.
Our design plans for malicious servers, and SDL clients will rotate their requests to whatever SDL servers that are up, instead of getting "stuck" on one malicious SDL server.
NOTE: Users with high privacy requirements SHOULD NOT USE COMMUNITY SERVERS and instead run their own SDL server. That is the only way to assure privacy at the same level as using a full node.
@onryo this code is mostly done, need your new host, and some "retry if down, or the next" logic
@onryo @jahway603 you added your servers to the static list of "Default servers" a user can choose, but that just let's users choose a single static server for all requests. If it's down, SDL doesn't work. This issue is important to do for the 1.4.1 release, so we rotate around our API requests to different servers
@onryo @jahway603 I am actively working on this and could use help testing it when it's ready 🤘
This is now working in 1.5.0 release.