wait, as so the ntfy.sh Android client will cause excessive battery drain with non-default servers because they use a persistent websocket connection for the notifications (with a non-configurable keep-alive interval) if you're not using their server?
The server already has webpush support, isn't that enough for low-battery-usage notifications?
Correction: IIUC it will do that for every server if you enable "instant delivery", but for non-default servers it cannot use firebase which is apparently less instant but not battery wasting?
speculation@lunareclipse You may already know this, but I wonder how much of this is people being confused by Android's rather terrible IMO UX for battery usage. It doesn't show how much percent of the phone's battery an app used, it shows the percent of the decrease it thinks an app is responsible for. (your phone battery dropped 10% over 10 hours, and it thinks the app used 50% of that). So this number naturally depends on how much or little every other app is using, even if the actual battery usage stays the same.
alternative software :)@lunareclipse It may be a little silly to host an xmpp server just to be a unified push distributor, but that's also an option with Conversations codeberg.org/iNPUTmice/up (Ejabberd also has a module now too).
