Philipp C. Heckel

There may be a race condition issue with resetting in-memory stats as well that is likely related to this race.

You should link https://gjson.dev/ in the docs. It's awesome. Here's a real Grafana alert that I get for ntfy sometimes: ``` {"receiver":"ntfy\\.example\\.com/alerts","status":"resolved","alerts":[{"status":"resolved","labels":{"alertname":"Load avg 15m too high","grafana_folder":"Node alerts","instance":"10.108.0.2:9100","job":"node-exporter"},"annotations":{"summary":"15m load average too...

So elegant and simple. Well done. I'll merge it tomorrow

Still fails ``` ⨯ release failed after 22s error=docker build failed: failed to build binwiederhier/ntfy:v2.9.0-armv6: exit status 1: #0 building with "default" instance using docker driver #1 [internal] load build...

Please provide more information. I have no idea what you mean.

I'd like that too, but honestly it requires too much work for too little gain. It does come up frequently, but it's likely going to break a bunch of things...

I'm going to try to take a look later this week.

For anyone using the ntfy.sh server and not a selfhosted instance: I am seeing lots and lots of rate limited (aka rejected) requests from various matrix instances. There are very...

> I'm using the matrix.org homeserver, and I don't get notifications until I open up the element app. In the ntfy android app, it says `im.vector.app (UnifiedPush)`, so I assume...

ntfy.sh + Element works for me and many others. Try re-subscribing in Element by re-selecting the Notification method. Also: I updated the Matrix code in ntfy a little which will...