You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if Molly could offer UP functionality out of the box through a bundled MollySocket server. Such a public server could be airgapped for better security.
Offering such a service at volume would bring economies of scale and the community at large should be able to cover the costs of server deployment.
Given the various known issues with FCM notifications and the problem of each app installed on a device needing its own WebSocket connection, UP becomes the only scalable and practical solution going forward for all open source apps. By allowing users to start using UP with Molly today, this community would be charting the path forward for the entire open source world on Android.
Even better, if Signal is willing to support UP - same as it supports FCM/websockets, it would be FCM/UP/websockets, then the battery drain issue goes away(mostly) and molly gets UP support automatically.
@ghost while not bundled within mollyim-android, you can still setup and use mollysocket-fly for free. This fixes high battery usage by molly(related to websocket connection).
Is there an existing request for this?
Feature description
It would be nice if Molly could offer UP functionality out of the box through a bundled MollySocket server. Such a public server could be airgapped for better security.
Offering such a service at volume would bring economies of scale and the community at large should be able to cover the costs of server deployment.
Given the various known issues with FCM notifications and the problem of each app installed on a device needing its own WebSocket connection, UP becomes the only scalable and practical solution going forward for all open source apps. By allowing users to start using UP with Molly today, this community would be charting the path forward for the entire open source world on Android.
This would also resolve #126
The text was updated successfully, but these errors were encountered: