Whisperfish - The unofficial SailfishOS Signal client

[rubdos]

@WT.Sane: Interesting, could you provide some logs from you receiving a group message somewhere?

@petrescatraian

Is there a way to import the chat history in Whisperfish? Sorry if it’s something obvious that I’m missing, I looked everywhere amd I didin’t find that option and read through multiple forum posts.

Nope indeed, no options for now for import.

[WT.Sane]

@rubdos

@WT.Sane: Interesting, could you provide some logs from you receiving a group message somewhere?

How would I do that. You never know when a message arrives and where would I find the logs?

Some messages come through but only a short time after I wrote something.

[Arrina]

I could not recieve messages in groups from persons with whom I did not have prior direct messages in Whisperfish. When I wrote to them and manually accepted the contact, I was able to recieve messages in the groups from them.

[rubdos]

@Arrina, that’s good data and I think I know what’s going on here. @WT.Sane, probably same issue. Would either of you want to try a build tomorrow to see whether it’s fixed?

[WT.Sane]

@rubdos

@WT.Sane, probably same issue. Would either of you want to try a build tomorrow to see whether it’s fixed?

Yes. My pleasure.

[j6s]

I have a large group conversation with 658 members. The app becomes incredibly sluggish when opening that group and it’s details. Scrolling the message window is smooth, but scrolling the List of members is not.

Without knowing many details, I suspect that rendering all members is a bit resource intensive. Maybe a solution could be to only render the first 50 members with a button to load more.

[JE281]

its not just the member list. Having huge groups is generally very ressource heavy. If you tried reacting to messages you will see that it can take minutes. Its just a limitation as of now I think.

[rubdos]

@j6s

Without knowing many details, I suspect that rendering all members is a bit resource intensive. Maybe a solution could be to only render the first 50 members with a button to load more.

I’m going to use you as a test case. 658 is madness. But Silica shouldn’t have any issue rendering 658 items, that’s just slop on our end.

@JE281

its not just the member list. Having huge groups is generally very ressource heavy. If you tried reacting to messages you will see that it can take minutes. Its just a limitation as of now I think.

Indeed. This is first on my TODO list after fixing the remaining missing messages in groups. And I’m quite confident that Draft: reset stale identity and retry DME on UntrustedIdentity (!822) · Merge requests · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab fixes it; at least on my device I see waaaaay more stuff now.

[j6s]

I’m going to use you as a test case. 658 is madness. But Silica shouldn’t have any issue rendering 658 items, that’s just slop on our end.

Sure - If I can help test a build or something, just @ me in this thread or send me a DM. I got to admit, that having 600+ people in a group is sort of an edgecase though

[rubdos]

Thanks! Took some notes at Large groups render slow in group overview. (#824) · Issues · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab

[Dequei]

Is there an option to load a backup?

[rubdos]

Nope, sorry! It’s a lot of work to implement, and not a priority atm.

[WT.Sane]

Somehow my groups seem to get more and more posts esp. after I wrote something.

The problem seems to happen less often. I did not change anything. Maybe the number of group members that are also one on one contacts plays a role?

[rubdos]

Your observation and hypothesis are both consistent with my findings, and the fix should be in Draft: reset stale identity and retry DME on UntrustedIdentity (!822) · Merge requests · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab

I’d like to get sender keys merged too before releasing it, which should fix most performance issues in groups as well.

[WT.Sane]

Thank you so much. It was a good decision to go back to Whisperfish with my J2.

[j6s]

My signal message history is quite extensive and I have always been very meticulous about not loosing it. In order to (somewhat) preserve the history on Sailfish, I built a small tool in order to restore messages from signal desktop to Whisperfish: GitHub - j6s/harbour-whisperfish-message-restore · GitHub

AI Disclosure: All code was written by myself, even if it is somewhat sloppy. I have been experimenting with Jetbrains line completion, which was very disappointing, leading me to write most of what was (incorrectly) suggested myself.

[joboe]

As from today I am unable to reach my contacts via Whisperfish. The message is sent (one hook), but not successfully transmitted to the reciepient. It works via Signal (Android app).

[JE281]

I think it would help to debug this if you could enable advanced debugging options below developer options (last entry) in Whisperfish settings and reproduce the issue and save the log with this:
devel-su journalctl --identifier=harbour-whisperfish > log.txt
The log will be under /home/defaultuser/log.txt

[joboe]

For sure I will do this - but maybe it is already a known error right now…as soon as @rubdos or @direc85 want me to create a debug log, I’ll do so.

[rubdos]

@joboe If you confirm that you didn’t re-register or so, yes please, logs. I have a suspicion and very little time sadly.

Yes, just logs, my suspicion can’t be true, luckily Is it with all recipients? I’d suggest to DM the log, not paste it public. Modern logs should be relatively clean, but you probably should still try to clean them up a bit: Home · Wiki · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab