XMPP

431 readers

1 users here now

XMPP (aka Jabber) is the community-owned standard for real-time federated messaging.

For a quick start click here

JoinJabber.org support chat

JoinJabber.org admin support chat

XMPP.net Provider List

Also see JoinJabber.org FAQ

founded 2 years ago

MODERATORS

poVoq@slrpnk.net

pep@slrpnk.net

nicocool84@sh.itjust.works

Molly-UP deprecation (poptalk.scrubbles.tech)

submitted 7 months ago by pootriarch@poptalk.scrubbles.tech to c/xmpp@slrpnk.net

6 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] pootriarch@poptalk.scrubbles.tech 1 points 7 months ago (1 children)

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)?

[+] TechnicallyColors@lemm.ee 2 points 7 months ago* (last edited 1 month ago) (1 children)

[deleted]

[–] pootriarch@poptalk.scrubbles.tech 1 points 7 months ago

Unfortunately this is a non-starter for me at the moment.

Molly/FOSS/UP is deprecated and frozen at a prior version, so I'm at risk of vulnerabilities.
Upgrading to current Molly-FOSS requires a VAPID-capable mollysocket (1.5 or higher).
mollysocket cannot be upgraded with a simple cargo install. cargo throws error[E0599]: no function or associated item named ec_gen found for struct PKey<_> in the current scope

Searching for PKey::ec_gen() points to openssl. mollysocket has at least two dependencies that it doesn't declare, but we don't know how many.

You probably need to install some system packages, like libssl-dev libsqlite3-dev.

The best-case scenario is that libssl-dev is a lower version from what it wants, and that an upgrade would clear the problem. But since the dependency isn't declared, we don't know the minimum version. In my case it doesn't matter as I'm in a shared hosting environment and I can't just change system packages.

I'll need to figure out a way to go back to vanilla Signal, and a way for Signal to recognize that I do in fact have Google Play Services. The Molly docs explain only moving to Molly, not away from it.