This pull request add UnifiedPush support to Molly. (Issue #88)
There will still be some changes and some elements are still missing, but it can now start to be reviewed and tested.
It requires a M...
It is pretty common when starting to use apps that don’t depend on Google services to not get notifications. Many struggle with inconsistent and sub-optimal notification strategies such as background sync via polling or a custom notifications service and need battery optimizations turned off. UnifiedPush allows for push notifications from a server or your choosing so those other methods don’t need to be used.
The app was generally able to send notifications just fine, through whatever way they used back when I tried it. Probably a websocket, since UnifiedPush is only now being introduced.
Just when I used the database encryption specifically, the app was fully locked down, and wouldn’t send notifications out, then.
I’m just wondering if that is by design, or if I maybe just missed a crucial setting.
It is pretty common when starting to use apps that don’t depend on Google services to not get notifications. Many struggle with inconsistent and sub-optimal notification strategies such as background sync via polling or a custom notifications service and need battery optimizations turned off. UnifiedPush allows for push notifications from a server or your choosing so those other methods don’t need to be used.
The app was generally able to send notifications just fine, through whatever way they used back when I tried it. Probably a websocket, since UnifiedPush is only now being introduced.
Just when I used the database encryption specifically, the app was fully locked down, and wouldn’t send notifications out, then.
I’m just wondering if that is by design, or if I maybe just missed a crucial setting.
ntfy FTW.