The workaround would be even easier if the “shut down whisperfish” button would be on top of the settings page. I do realize that it doesn’t make sense to target an easier workaround if instead the issue could be fixed, but I experience to use this button quite often
Why? A top-to-bottom swipe is enough to shut down Whisperfish, afterwards just open it again…
1 Like
Not for people with the “daemon mode” enabled 
But it should actually be rather easy to add a restart button on the pull-down in the main view, which force-restarts the connection.
6 Likes
Done.
8 Likes
I never understood why WF sometimes didn’t synchronise with Android-Signal properly. Now I know
2 Likes
Looks like someone found a real solution too: Close websocket when keepalive are no longer received by fraukappayuwe · Pull Request #347 · whisperfish/libsignal-service-rs · GitHub 
That should really take out a major annoyance for many WF users!
13 Likes
How does it work with the check marks? I guess one check mark means that Whisperfish could send the message, a double check mark means that the message has reached the receiving client. Am I right?
Is there also a read receipt?
What does it mean if there is a double check mark which is lighter (or bold) than the other (see screenshot)?
Quite sure you’re right, yeah.
To answer your last two questions: That is the read receipt function; 2 white checkmarks is received and read, 2 greyed checks is received but unread afaik.
1 Like
That’s how I remember it too!
2 Likes
I think that (read/unread) should be better distinguishable from each other, maybe use different colours?
Or would colours interfere with Ambiences?
6 Likes
I see no difference, the two hooks have always the same color.
2 Likes
It’s the same for me…
Maybe the “read hooks” can be bold?
Maybe you have Whisperfish as a secondary device? I also have that and I think Whisperfish is for some reason not able to display read reciepts on secondary devices (it says in the setting that this can only be changed on the primary device, but I have my primary device set to enable read reciepts and it still doesn’t show them in Whisperfish)
3 Likes
Yes, it is my secondary device. Allright, that makes sense!
Since that system has only been recently implemented, you may be able to fix that by disabling and then re-enabling the read receipts on your primary device. Just going on a hunch here.
1 Like
Agreed; you’ll at least want to enable Read receipts on your device. (see picture)
(and probably have a good look at other settings, because that’s what they’re there for! 
)
I tested this yesterday - disabled and then reenabled read receipts on the “primary device”, but I still don’t see them in Whisperfish
2 Likes
Same here (20 chars)
