Zurück

@fiee @mollyim With the old version, if there wasn't a MollySocket server, Molly felt back to the websocket. There were some warnings but the UX wasn't enough to make the user aware, and some users were thinking they were using UP while using the websocket.

This is a reason why we made the QR code mandatory. MollySocket is used to "extend" Signal servers, to push to your push server (your Nextcloud server in your case), see: https://github.com/mollyim/mollysocket?tab=readme-ov-file#overview

Sorry for the confusion

@S1m
Thanks for the answer.
But Molly is registered in NextPush
It works with Tusky and Element.
Why does Molly need special treatment?

@mollyim

@fiee @mollyim Because Signal servers don't support webpush (yet ?). So we use mollysocket to add this support for our account, as you can see on the overview shared above

@S1m @mollyim

Thank you. I’m trying to understand the instructions…

@S1m @mollyim

Next step: mollysocket systemd service fails to start.
Where can I find the log to look for the reason?

@fiee @mollyim what happens when you try to run `/opt/mollysocket/ms` ?

@S1m @mollyim

Oops, the symlink ms was missing. Too obvious… The service runs now, nginx must wait until tomorrow.
Thanks again!

@fiee @mollyim You're welcome