Improve peer uptime metrics calculation by checking reliable public domains

[dilshat]

We can periodically check public domains such as google.com and a few others and report results to Bazaar.
Based on this Bazaar can calculate peer uptime better

[dilshat]

by @niclash :

Point is basically to report availability over a much longer period than the reporting interval to Bazaar.
For instance, in the metrics, provide availability for last 24 hours, 7 days and 1 month.
And Bazaar can choose how to present that, but otherwise doesn't need to rely on heartbeats
Because it is more likely that Bazaar is down

[dilshat]

https://crunchify.com/how-to-get-ping-status-of-any-http-end-point-in-java/

[dilshat]

This approach has potential problems. Malicious user can edit /etc/hosts file and setup local counterparts of such public servers to respond. Instead of this, would not it be better to have Bazaar send ping commands to a random public server known only to Bazaar or rely on heartbeats to determine peer availability?