Frank Elsinga

Likely depends on https://github.com/louislam/uptime-kuma/pull/5193 being reviewed/done first. How to implement this is two PRs: - one to move groups out of `monitor.js` into their own `monitor-type` https://github.com/louislam/uptime-kuma/pull/4395 - possibly also...

> Since this is your PR, do you plan on finishing it, or is there something to be done there still besides tests? From my POV this is finished. Yes,...

> we never got enough GPU capacity We need to communicate this better in the future. OpenSource@TUM has funding. I have put a 3090 in "our the usual place". That...

From my point of view, there is nothing left to review. There are a few threads (like https://github.com/TUM-Dev/gocast/pull/1380#discussion_r1804770695) which are not quite resolved, but from my point nothing blocks merging.

Let's add this to our wiki (i.e. where we document the other competitors offering similar services) instead. https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install#unofficial--experimental

If the migration we did for the dns monitior is applied to http, this should be included by default. Feel free to raise a PR. Our contribution guide is here:...

> ENOTFOUND Consider enabling NSCD in the settings to make the DNS resolver less likely to jeject you as spemmy. This has the downside of caching dns queries, which you...

In that case please check the TTL of the DNS record. If the TTL is really low, this might also happen

> Some DNS servers might reply with several IP addresses. Can you provie an entry to reproduce this with?

Will be resolved by https://github.com/louislam/uptime-kuma/pull/5588 in 2.1 by making the deadline configurable.