Frank Elsinga

Yes, as I said above: this issue was closed by mistake.

One thing that might be good to discuss is what groups on the status page really mean. I mean this: 

@Honorme94 This is an issue which has been resolved quite a while ago. Your issue is unlikely to be related => please open a new issue with reproduction steps

I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1844 If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If...

@Pranav-Lakhani I don't understand what you are referring to. Could you please translate what you meant using deepl.com? (your post probably got no coverage because it is not clear what...

@m-primo This comment was closed because it is a `help` issue. Probably these types of issues should be discussions instead, but that is a decision that only Louis can make...

@adm2k I think this issue is resolved. 1. you can block out timespans using maintenance windows. 2. you can use the http-keyword monitor. Could you please close this Issue, as...

@merlinsvk @nicuj0r @moodyblue @BAYERNOLI Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing what needs to be done...

Before somebody proposes a PR, we should discuss where this should be integrated: In an existing monitor or a new monitor. I could imagine this being a checkbox in the...

@ithakaa We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/1089 https://github.com/louislam/uptime-kuma/issues/2487 #3387 as there is no functional difference...