XMPP

404 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 5 months ago by pootriarch@poptalk.scrubbles.tech to c/xmpp@slrpnk.net

8 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.

top 8 comments

sorted by: hot top controversial new old

[–] TechnicallyColors@lemm.ee 2 points 5 months ago (2 children)

I just did this, and these were my rough steps:

Backup from Molly-UP
Write down the code
Install normal Molly from FDroid (you don't need to remove Molly-UP yet)
Open normal Molly and import the backup, log in to your account etc
In your mollysocket instance, run mollysocket vapid gen and use the key as MOLLY_VAPID_PRIVKEY environment variable in docker compose, or however you're running mollysocket.
Go to notifications and change the notification type to UnifiedPush, and scan the QR code from your mollysocket instance. (I was having trouble scanning the QR code when it's printed out via CLI, maybe because it was white on black, but the QR code from the web server page (port 8020) worked)
Uninstall regular Molly-UP when you're ready

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.

[–] pootriarch@poptalk.scrubbles.tech 1 points 5 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 5 months ago (1 children)

I think it is dependent on it. The only option for connecting to mollysocket is now QR code, and QR code requires VAPID.

[–] pootriarch@poptalk.scrubbles.tech 1 points 5 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.

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

thank you! i have to look at mollysocket then; i don't remember the vapid/qr step, so might have to upgrade it also

[–] kixik@lemmy.ml 1 points 5 months ago (1 children)

I don't see that, neither I see a note on its github repo. The only thing I noticed is something I haven't paid attention before:

Currently, UnifiedPush is unavailable for linked devices.

Which is totally counter productive, and explains why even by setting unifiedPush through ntfy molly keeps draining battery, :(

The official F-Droid doesn't offer Molly, not even the so called FOSS by its author. And the Molly-FOSS repo from the author still offers Molly (Unified Push). Am I missing something from the "Molly-UP deprecation" referred? I'm not seeing such a thing.

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

i surely didn't explain well. to my knowledge there are three mollys. the standard one with google services blobs, the -foss that has no blobs and presumably has to use websockets, and the -up (-foss-up?) that can do unified push, though it doesn't have to.

i forget whether foss and -up were in different repos to each other. but without my changing any repos, molly(-foss)-up updated itself to 7.23.1-1.up1-foss. this is behind the 7.26 of -foss. it displays a dialog that says it's deprecated, and since it's left backrevved, isn't likely getting security updates. clicking install sends you into the hole i described at first.

i do believe this path is working and that my notifications are coming through my xmpp account, not websockets. but i haven't traced it to prove it is so.

[–] kixik@lemmy.ml 1 points 5 months ago

Upgrades happen a different times it seems, depending on the phone, :( Yes, I notice exactly the same... I'm trying to ditch signal any ways, perhaps the right time. But the instructions someone share seem the appropriate ones.

Thanks !