-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Definition of "healthy" #38
Comments
@unixfox Thank you for the links. However, these solutions are information-only, meaning it's nice to have them in the table, but they are not changing the redirection logic if I understand that correctly. So, this isn't solving the core problem which led me to open this very issue. |
we can't implement the frontend feature if the backend feature doesn't exist. |
Sure, but why closing this issue instead of letting it open, waiting for the linked PR to be merged and then take the information from the instance API? |
we will create a separate issue when the backend will be done. for the moment there are more urgent issues to solve. |
Hope, I'll notice when the time comes … |
How is the health percentage calculated?
A server itself can respond every time just fine and quite on time, but the instance can respond with errors caused by Google regularly.
When redirected to these instances, this can be pretty annoying. It would be nice if that would be taken into account when redirecting.
Would there be a need for URL parameters (geolocation/region, software version preference and such)?
The text was updated successfully, but these errors were encountered: