@rakoo@delta@fell I used Signal on websocket without FCM and had a feeling that battery life is not perfect. I believe Signal spent some effort not to do it the stupid way.
@lyyn@rakoo@fell in our measurements delta manages to consume less battery when there are no gplay services as it can do efficient idling. Google fcm and play have their own overheads even if their purpose it to prevent apps from consuming too much battery. With the upcoming FCM Push Service integration for Chatmail users we might redo these measurements but there is a wide variety of setups on Android so not so easy.
@delta@rakoo@fell Hmm, if you are integrating FCM into Chatmail do you have plans to add UnifiedPush support? I saw a discussion thread on your forums, but it was closed 3 years ago.
Not a delta dev, just my opinion: UnifiedPush is useless here. Either you want to integrate with FCM because reasons, or you use the native IMAP IDLE that doesn't consume much. There is no need for an intermediary because there is no need to make it pluggable.
UnifiedPush is useful for apps that don't use a protocol with a proper push mechanism even though it's important for the app to work. If anything it's a confirmation that HTTP is crap and should not be used *that* much.
@delta@fell
Not a delta dev, just my opinion: UnifiedPush is useless here. Either you want to integrate with FCM because reasons, or you use the native IMAP IDLE that doesn't consume much. There is no need for an intermediary because there is no need to make it pluggable.
There already is a standard though for sending messages, that doesn't consume much and can interleave multiple payloads, it is XMPP and is specified by the IETF. In fact FCM allowed XMPP at some point. I'd agree with you that XMPP should replace all those reinventions and both Google and Apple should use it, but alas.
It totally makes sense to use UnifiedPush instead of websocket though, because websockets are a hack because using HTTP here is silly, and it requires specific machinery. It's easier to rely on another party. Deltachat isn't the same: there is something that works natively, that should be the preferred way of doing notifs
@delta@fell@grishka
There already is a standard though for sending messages, that doesn't consume much and can interleave multiple payloads, it is XMPP and is specified by the IETF. In fact FCM allowed XMPP at some point. I'd agree with you that XMPP should replace all those reinventions and both Google and Apple should use it, but alas.
Lyyn ☮️🦄 #2024-02-16, Mastodon doesn't use UnifiedPush, it uses a WebPush -> FCM relay. There is currently no way to receive push notifications without Google services or at least MicroG.
@lyyn @rakoo @fell in our measurements delta manages to consume less battery when there are no gplay services as it can do efficient idling. Google fcm and play have their own overheads even if their purpose it to prevent apps from consuming too much battery. With the upcoming FCM Push Service integration for Chatmail users we might redo these measurements but there is a wide variety of setups on Android so not so easy.