From the Conversations MUC, it seems like Conversations renews when the endpoint is less than a day from expiry. This makes it always retry a new endpoint, even when the maximum expiration of 1 day is set in mod_unified_push.
Many UP-compatible Android apps (e.g. in my case Element X) checks for push registrations upon startup. With the low expiration, this effectively make it register a new endpoint whenever it is launched, which seems very unnecessary.
Conversations' reference implementation, up Rewrite Proxy, implements 7 days of expiry. Ntfy does 60 days.
Therefore, I'm advocating for increasing this expiration value to a default of 7 days with a maximum of 60 days.
From the Conversations MUC, it seems like Conversations renews when the endpoint is less than a day from expiry. This makes it always retry a new endpoint, even when the maximum
expirationof 1 day is set in mod_unified_push.Many UP-compatible Android apps (e.g. in my case Element X) checks for push registrations upon startup. With the low expiration, this effectively make it register a new endpoint whenever it is launched, which seems very unnecessary.
Conversations' reference implementation, up Rewrite Proxy, implements 7 days of expiry. Ntfy does 60 days.
Therefore, I'm advocating for increasing this expiration value to a default of 7 days with a maximum of 60 days.