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.
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.
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.
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 
Important note 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.
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! 
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.
Thank you very much work great
I only have a voice call to give up Molly
Thanks
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.
This doesn’t seem to be fully fixed, unfortunately! It still keeps resetting my read markers and typing indicators to off.
Are you running Whisperfish as primary device? If so, have you tried relinking Signal Desktop?
No, only as a secondary device because I had trouble reregistering with Whisperfish as the primary client. My primary client is the official Signal app running on the same phone.
@rubdos as per your blogpost Building RingRTC and webrtc for Whisperfish and description in Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab, it seems possible to build Whisperfish with WebRTC support (voice & videocalls), but AFAIK that’s not in the distributed package?
I’ll make an update to the blog post to clarify this: Whisperfish is built with RingRTC support, but no features are implemented yet. The only thing which is implemented, is showing the notification for an incoming call (as “missed call”). This already uses the RingRTC package that I mention in the blog, because that package contains the packet decoding and ringing state machine logic.
Send me a bucket of motivation and energy (20L should suffice) and two weeks of holidays, and we can call on WF… (some sarcasm implied).
Thanks for the clarification, videocalls are indeed a big effort to implement! I contributed a big chunk of audiocalls to a Jabber client long ago, so I know for real. Still, thanks for what is out there so far in Whisperfish!
One Question:
Until now, I have registered Whisperfish as a secondary client, so I’m forced to start/open new chats on the desktop/Android app first. When registering Whisperfish as the main client, is that still necessary, or does it work differently?
It works the same way, i.e. you need to start new chats on another (secondary) device of yours or get the other party to message you first.
I wonder if it would be possible to store whisperfish attachments to the sd card. All the images and speech messages pose a severe strain to the limited internal memory of my device.
You can! Edit .config/be.rubdos/harbour-whisperfish/harbour-whisperfish.conf and change attachment_dir= to whereever you want. You need to make sure the path is readable and writeable from a Sailjail point-of-view. After the change, new attachments will go to the SD card, and the old ones stay in place.
We didn’t really implement moving attachments yet.
That’S great. I see that the Permissions section in the .Desktop file already contains Downloads and UserDir, so a subfolder of Downloads on the sdcard should be fine?