Whisperfish - The unofficial SailfishOS Signal client

Please keep it, i think daemon mode is really useful as , afaik there is no “push” capability on Sailfish native.

1 Like

Yeh, I’m aware that there are plenty of people using it… but I’m thinking in terms of the new user influx due Jolla Phone:

  1. Only have it in the OpenRepos/Chum versions (and not on Harbour)
  2. Document it way better
2 Likes

Looks like @manuel.sailfish found a very recently reported issue: fix: update link device params with spqr by dudufalvo · Pull Request #415 · whisperfish/libsignal-service-rs · GitHub, which means that linking is broken altogether, but this will be fixed in the next version of Whisperfish! :slight_smile:

I’m quite busy until the 17th, but I will with high probability join Next meeting for French-speaking Sailfish OS users : 21 March 2026 in Lyon for a bit of a hackathon, I’ve heard!

4 Likes

Wait, are you trying to push Whisperfish in to the Harbour? I thought there would have been some rule which makes that impossible, but would definitely be beneficial for new comers!

Some Day™ :slight_smile:
We want to push Whisperfish to fit within the rules, sooner rather than later. We’ve had the rpm validator in the CI pipeline for years now… Better make the pipeline pass soon!

5 Likes

Reactions to messages from other devices doesn’t show in Whisperfish (primary device) any more. The other way works fine.

Yep, fixed upstream! But thanks for reporting :slight_smile:

2 Likes

Amazing! Tho, I think it is quite accessible still from storeman. Most of the users will need to install it anyway. But it would definitely be amazing to have one of the most used apps in Harbour :slight_smile:

2 Likes

I think introducing it was a really great idea as it makes Whisperfish really usable as a daily-driver (for me at least).

I think this probably not a good idea. People coming from other phones (so the new users you mentioned) are used to their messages arriving with push notification, even when their app is closed. So, removing that feature for all of the new users will just make them unhappy with Whisperfish because “there are no notifications”.

1 Like

I’ve got the same problem. tested different versions of whisperfish, reinstalled sfos three times, nothing works….

@flinkevent, same issue as above ^
The latest version on the main branch should fix this: Package registry · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab

I understand the concern. Then again, Harbour doesn’t really allow user services, and it’s causing a lot of confusion. I personally like the idea where a closed app is something that doesn’t run. There are just so many cases where WF crashes, and you lose your notifications, or people think that “restarting WF” means the same regardless of whether the daemon mode is enabled, … It’s quite a complicated issue to be honest.

6 Likes

Hi folks! The ETH team of prof. Kenny Paterson presented two vulnerabilities on Signal yesterday on the IACR RWC conference, together with researchers from Max Planck Institute and Radboud: https://iacr.org/submit/files/slides/2026/rwc/rwc2026/29/29_slides.pdf (check slide 33!)

They contacted us some weeks ago, because they were quite sure the same vulnerability existed in Whisperfish, Flare, and family. The issue was patched in beta 39, within the vulnerability disclosure window. Signal patched and released it before us, but we were still taken in the loop. I’m quite happy with how the collaboration went here, and I’m quite happy that we’re taken serious enough to be contacted for such reports!

Happy whispering! :speech_balloon:

28 Likes

Wow, congrats again! I got a lot to do with vulnerability management and patching non-original software before the original vendor does it is quite outstanding! :partying_face:

3 Likes

Oh no, should’ve mentioned: Signal had it silently patched before us! :wink:
I edited my post to reflect that.

4 Likes

Aaamazing collaboration! Super glad that there is this much of “doing it together” mentality :slight_smile:

4 Likes

Anyway - excellent job! :blush:

2 Likes

Hi there all,

Let me hope I’m posting this in the right thread. I’m trying to add Whisperfish as a secondary device on SFOS 5. My main device run’s Molly. Whenever I’m trying to scan the QR Code from the main device, it mimics that it seems alright and on Whisperfish I’m getting this error mesage:

Error
Failed to setup Signal client

Any clues at where to potentially debug a bit?

Thanks a lot,
Regards,

We need to keep our “known issues” better updated, it seems:

@obuno, same issue as above. Reset Whisperfish, and use the latest main branch version from above. Or wait on the next version! :slight_smile:

Thanks a lot for your update @rubdos / I think that the latest version in the repo is indeed what I’m currently using (setup/updates from openrepos), harbour-whisperfish-0.6.0.beta_.39-1.aarch64.rpm / I’ll wait a bit then – thanks again !