Frank Elsinga

> Obsolete by #2720. @chakflying Does this mean #1074 should be closed or just that this fix is obsolete?

@eazylaykzy @0xgui @sgeneralgrievous Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder and adds no productivity. [We use 👍🏻 on issues to...

@mathiskir I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1050 If you agree please close this issue, as issue-management is harder with zombies hanging around. If you disagree, what is the...

@mathiskir We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #1050 as there is no functional difference (maybe just...

@jensneuber Just checking in: What is needed to get this PR ready for review? (apart from a pretty brutal rebase) Is there something I can help with? Asking the hard...

@jensneuber given that #2915 is [nearing the merge](https://github.com/louislam/uptime-kuma/milestone/31), would you consider closing this PR? Is there something from this PR that should be included in #2915?

@alexandernst @tiagogoncalves-7egend @initpwn Please refrain from posting `+1` / requests for update-things on PRs, as this makes reviewing it even harder. For updates, there is a subscribe to this PR...

I am going to close this PR. Sorry for the work that went into this PR. At this time, I don't believe the problems that exist with the current implementation[^1]...

@bertyhell given that we are currently using Weblate for translations, is this PR still relevant? (Should it be closed?)

Given that what we think of as a thing that can notify and what cachet expects sets statuses are so different, I see not merging this as a better approach....