Gregory's Server@karma @signalapp what's the use case for this? It's likely a lot of work that an extremely small number of users would use.
If you use Google Play Services with Signal no message data is sent via push. You can also use the app without Play Services, albeit with a battery drain
@derekmorr @signalapp I understand that messages are not delivered through notifications. Instead, Signal servers send a message to the application saying, "Hey, wake up, you have something to do."
why UnifiedPush should be implemented?
1. Signal promotes itself as a privacy-focused app. messages may not be sent directly but metadata is still generated so it can and will be utilized
2. The existence of mollysocket, which has over 62,700 container downloads on ghcr.io only, indicates that there is a demand for this
3. Implementing UnifiedPush is not complicated. There are libraries for this protocol (implementing both client and server functionality)
@derekmorr @signalapp I understand that messages are not delivered through notifications. Instead, Signal servers send a message to the application saying, "Hey, wake up, you have something to do."
why UnifiedPush should be implemented?
1. Signal promotes itself as a privacy-focused app. messages may not be sent directly but metadata is still generated so it can and will be utilized
2. The existence of mollysocket, which has over 62,700 container downloads on ghcr.io only, indicates that there is a demand for this