Post #2768154
2023-12-11 23:26 UTC
@Mer__edith@mastodon.world How does it end up being battery-destroying? Shouldn't it just be waiting on a socket that has no data until there's a notification to be processed, with the TCP keepalive set on the socket options so kernel rather than userspace deals with stupid NATs that would otherwise drop it?
Replies (1)
-
@ck@chaos.social 2023-12-12 14:54
@dalias@hachyderm.io There are a couple of options for notifications. The most battery saving design is to have your app being woken up whenever a notification is received. This way, you app does not use battery while there is nothing for it to do. The dominant solution in this space is integrated into Google Play (proprietary). The opposite site of the spectrum, and the solution Signal chose, is for the app to require permission to stay awake all the time polling for notifications. @Mer__edith@mastodon.world