Frank Elsinga

@Pretender1988 > The only issue is the case: if it is still up and running but it should not! it will not notify me. But this is already a nice...

> it looks already good. The only issue is the case: if it is still up and running but it should not! it will not notify me. > Maintanance mode...

@pkishino This issue has been closed because it was raised with the `help` tag. Please open an issue with more details than the current issue. If you decide to do...

I used https://hub.docker.com/r/linuxserver/jackett/ and getting curl to cooperate was a bit harder: ```bash curl -v --cookie-jar -b cookiefile --junk-session-cookies --location http://localhost:9117 ``` Resulting log ```log * Host localhost:9117 was resolved....

@mabed-fr 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 and as there is no functional difference (maybe...

Closing as @timrabbetts did not respond and at this point I don't think he will ^^

Related #2505

https://github.com/louislam/uptime-kuma/issues/2715#issuecomment-1416648708 and https://github.com/louislam/uptime-kuma/issues/2715#issuecomment-1416889427 have proposed workarounds around this current limtation

I manually went through all German entries and updated all opening times. Given the amount of time this took me this is not scalable or doable at all. This system...

Related https://github.com/TUM-Dev/NavigaTUM/issues/586 => unshure if the spreadsheet changes the mergability of said data and if waiting until I can get https://github.com/TUM-Dev/NavigaTUM/pull/670 fully debugged + shipped is a better call.