F-Droid just pushed a Molly-UP update that appears to only add a deprecation warning, and that holds the version number below Molly-FOSS.
There are no instructions. The Install link points to the repo, which F-Droid just notes that I already have.
In the past I have completely lost Signal history twice, once from reinstalling Signal itself but it refusing to read the backup, and once from trying to upgrade from Signal to Molly but having a backup versioned in the wrong direction.
Is the safe process for replacing Molly-UP written down anywhere? I would strongly prefer keeping Unified Push, but I feel like I’ve been told to walk into a dark tunnel.
I just did this, and these were my rough steps:
mollysocket vapid gen
and use the key asMOLLY_VAPID_PRIVKEY
environment variable in docker compose, or however you’re running mollysocket.No real trapdoors or anything; I spent the most time trying to get the QR code to scan before finally getting it to work via the web server page.
OK, the VAPID key is new and it’s mentioned but not documented (other than to say it’s used if ‘it supports it’). Is Molly now dependent on the QR code and VAPID for configuration (meaning I couldn’t attach it to the pre-1.5 mollysocket that I have now)?
I think it is dependent on it. The only option for connecting to mollysocket is now QR code, and QR code requires VAPID.