@masoud Both have direct connections to their respective servers because #GrapheneOS comes without Play Services. Both apps prompted me for exemptions to "Battery optimizations" which I granted.
On the sending side I made sure (by looking at the double ticks ✅ ) that the messages were delivered instantly.
@daniel
I wonder if this is related to the bandwidth/power optimizations that XMPP clients/servers support (e.g. CSI) or just general app bloat. @masoud
@mattj@daniel@masoud
XMPP by its very nature is a protocol that effectively uses "notifications", as it pushes XML stanzas over a channel.
(so as the mobile is almost certainly using some form of NAT, as long as some form of pinging below the timeout of the NAT happens, everything is fine).
So for XMPP not having Google notifications should make little difference, I don't see how an XMPP client/server would even use them.
Now Signal, OTOH, I have no idea what it does. 🤷
@mattj@daniel@masoud
XMPP by its very nature is a protocol that effectively uses "notifications", as it pushes XML stanzas over a channel.
(so as the mobile is almost certainly using some form of NAT, as long as some form of pinging below the timeout of the NAT happens, everything is fine).
So for XMPP not having Google notifications should make little difference, I don't see how an XMPP client/server would even use them.
Gregory's Server
@masoud Both have direct connections to their respective servers because #GrapheneOS comes without Play Services. Both apps prompted me for exemptions to "Battery optimizations" which I granted.
On the sending side I made sure (by looking at the double ticks ✅ ) that the messages were delivered instantly.