Whisperfish - The unofficial SailfishOS Signal client

You could of course use the OpenRepos site (API?) to actually check for a new version.

Storeman has a kind of 'quick update check ’ function that apparently does not go through rpm/pkcon/zypper.

There is a privacy/phoning home aspect to such a check though of course.

4 Likes

It’s quite difficult to understand what you mean here. Voice and video calls are currently not implemented. Ringrtc is linked in Whisperfish to be able to decode call notifications, such that we can display them as “missed call”.

If you want to compile (our fork of) ringrtc yourself, you’ll have to show me which instructions fail for you. You can build Whisperfish with –with calling to link to ringrtc.

Apart from what @direc85 just said: I think we should make sure that the nag message is linked to the last known release at build time, instead of the build time itself. That way, Matti and I also get annoyed, and it’ll trigger us to make a release… As of the next release (which I hope to get out this week), the nag message will only appear weekly instead:

It’s exactly because of this that I want to avoid implementing such a check.

9 Likes

I apologize for the bad translation, I mean, is it possible to configure whisperfish with a feature of requesting and receiving a phone call Did one try this?

It’s not yet possible. As a general rule: the OpenRepos version is configured with all the bells and whistles. If it’s not on OpenRepos, and not documented on the FAQ, then it does not exist.

2 Likes

Whisperfish 0.6.0-beta.36 “Group effort”

The name (picked by @direc85) is kinda ironic: it refers to a huge effort regarding group update messages. Instead of “group was updated“, you will now get meaningful messages. It is ironic in the sense that this release was mostly a one-man effort: Matti did practically all the work on this release! Thank you Matti :slight_smile:

:warning: Important note :warning: If you use Whisperfish as the primary device (you registered with phone number using Whisperfish), you may have to re-link Signal Desktop. Remove the device from Whisperfish settings and add it again.

  • Feature: Properly handle most group update messages
  • Crash: Rendering message expiry indication
  • Regression: Fix opening own profile page
  • Regression: Fix fetching profiles
  • Regression: Fix synchronizing settings and configuration to linked devices
  • Regression: Show fingerprint correctly
  • Bug: Cover page messages no longer concatenate
  • Bug: Edited message now closes its old message notification
  • Bug: Linked device name shows correctly and can be changed
  • Bug: Update check notification is shown weekly (instead of every launch)
  • CI: Build time cut in half, from 2h to 1h
  • CI: Try to catch translation errors
26 Likes

Working great, thanks for the update!
I had to go back into my VM which is running Molly in order to re-enable the typing and read indicators, but this time they stay active and so far they keep working! :hugs:

1 Like

Thanks a lot for the update. My 10 III is registered as a primary device and it works great.

I registered a 10 as a secondary device and it works also great. At present there are no issues.

3 Likes

Thank you very much work great
I only have a voice call to give up Molly
Thanks

1 Like

With some tinkering, you should be able to have both Molly and Whisperfish on the same device! Just register one of them as secondary device, and then you can switch to Molly if you see a call incoming. :slight_smile:

6 Likes

This doesn’t seem to be fully fixed, unfortunately! It still keeps resetting my read markers and typing indicators to off.

3 Likes

Are you running Whisperfish as primary device? If so, have you tried relinking Signal Desktop?