Additionally, due to that devices can be "hanging" for a while without being unregistered after user ends usage of the mobile app, it may be desired to have a TTL for enabling push notifications for particular device.

We also have an ad-hoc command to list and disable push notifications for selected devices just in case if some device is stuck as enabled.

@kobit @wojtek Feature was implemented and tested locally. As the next step, we could deploy it on sure.im/tigase.im and verify its behavior on a real environment. Or should we use a different environment to enable this feature?

Wojtek, could you look at the documentation for this feature? is it OK? or we need to change something?

Feature was implemented and tested locally. As the next step, we could deploy it on sure.im/tigase.im and verify its behavior on a real environment. Or should we use a different environment to enable this feature?

I think testing on tigase.im/sure.im would be a good idea

Wojtek, could you look at the documentation for this feature? is it OK? or we need to change something?

Synchronised github repo and manually forced RTD build to make it up to date: https://docs.tigase.net/en/latest/Tigase_Administration/Configuration/_Configuration.html#push-devices-presence

1. is there any default for deviceRegistrationTTL?

Apart the docs look ok - I did some light editor change.

There is no default for deviceRegistrationTTL, so the value is by default null. With that we have the same behavior as previously - no TTL. The reason for leaving TTL disabled is that normally push components should inform XMPP server when it was not possible to deliver notification due to application removal on the users device or similar issue and that would result in removal of the entry from the list of push enabled devices/clients for the user hosted on XMPP server.