Frank Elsinga

@phinnay You want #1190 instead @jaxjexjox @R0GGER @mmaxwell5 @mingal Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing...

As @ligouras mentioned above, if you need such an option, you can use external api-providers (For obvious reasons, do a small security audit first, this is neither an endorsement nor...

> the scripts directly writes into the kuma.db Please use third party tooling like https://uptime-kuma-api.readthedocs.io/ instead

@moay (ping, as only you/Louis can close issues) Could you close this issue? We forgot to close it during the merging of https://github.com/louislam/uptime-kuma/pull/3253 which is included in the `1.23`-release. If...

Resolved by https://github.com/louislam/uptime-kuma/pull/3253

@JaneJeon This is being autoclosed as you chose the `help` Template. If the cloud provider has a healthcheck, you an monitor it that way. Otherwise I don't see what you...

@chris-ard The issue which caused this was either solved - in `v1.10.1` or - somewhere on the way - will be in `v1.23.0` as a lot of performance fixes like...

> @chris-ard The issue which caused this was either solved > > * in `v1.10.1` or > * somewhere on the way > * will be in `v1.23.0` as a...

> Related to #2280 Not related to #2280, but an offshoot of https://github.com/louislam/uptime-kuma/issues/128: Said issue being the one which goes into detail what systems need to be changed how to...

@evolucja Stauts-Subscription tracked in https://github.com/louislam/uptime-kuma/issues/916