active nets widget shows 0 nets when connected to backend that does not support the api

[kr8x]

io HamClock design guidelines / system principles are: 1) Do not continue to repeat api calls that are not supported since the hamclock ip address could be banned under fail2ban 2) Ensure that there is a mechanism in place to support interwork to earlier versions of ham clock backend that do not support the api. There may be older self-hosted versions out there

[wasatch-dev]

Any backends that want to continue to support HamClock beyond 4.23 should implement the OHB interface. The update interval is there to keep nets fresh and the check-in info fresh because it updates rapidly

[komacke]

I think we are going to avoid implementing a support matrix. We expect HamClock to be friendly (it says 0 nets) and the user presumably would not use the feature or move to a different back end.