Whisperfish - The unofficial SailfishOS Signal client

Applications
1337

You are amazing!

Unfortunately you will have to convince me a bit harder to reregister without a new build, cuz I don’t think a second incarnation will be appreciated by my contacts.

If the need arises that I must be in a group or two even with that shady persuasion, will the messages be merged in the next build? (Even though I hope to keep this “clean” for everyone else)

I can report that my work phone’s work identity works, and I got two checkmarks sending my deregistered self a message, after a restart. Can’t check reception now, but it got sent “somewhere”!

1 Like
1338

That would be the goal indeed. Not easy, but should be doable.

Same here. My guess is that the message queues only get removed after a certain time, but I’m too unfamiliar with the server code base for that.

1 Like
1339

Yeah cuz I was thinking if it’s easier to merge if the new account is unused, like a unidirectional vs bidirectional thing. Let’s hope we don’t need to find out.

I’m here for this, you know how to reach me when you have a build to test, and I’ll stall my contacts for as long as I can.

Thank you!

2 Likes
1340

Full disclosure: I have made a new (primary) account on my own device. I will still make a backup importer tomorrow. If you want to follow suite:

  1. Make a backup of ~/.config/be.rubdos/harbour-whisperfish and ~/.local/share/be.rubdos/harbour-whisperfish, move the directories away from that path.
  2. Follow the registration procedure

I am currently running a custom build, which includes the fix that could have prevented the issue, plus a patch that detects a failing camera (relevant on Xperia IV and V) on device linking. Both patches will be in the next release. That second patch is QML-only, so in theory you can apply it without building: Add text link fallback for failing camera capture (!674) · Merge requests · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab

7 Likes
1341

Nice!

Doesn’t the identity still live there, so this does not merge anything? Is that gonna be a part of the backup importer?

And the backup importer will be smart enough to re-number the messages so that old sessions remain legible, right?

I’m busy atm but is there a branch on gl I can try to build, or pipeline dump, or something if/when my family lets me?

1342

So this worked for me.
I’ve backed up my previous messages and can now receive and send new ones!
Thanks!

1 Like
1344

After registering you copied .config and .local/share/
?

1345

Hi there, not yet. My chats are clear except my new test chat after re-registering. @rubdos is making a backup importer for our old chats so I’m waiting for that.

1346

No, and you should never do that. This bricks your installation. This is why the backup import is so difficult to make; selecting which items you can safely retain, and how to merge them is quite an endeavour.

6 Likes
1347

Just a side note: after newly registering with WF and relinking SD (on a Linux laptop), all former messages are preserved in SD; for me this is enough. (I started a second SD with a backed up data dir at the same time but I think this is not correlated.)

2 Likes
1348

Yep, a relinked Signal Desktop indeed retains previous conversations! Pretty useful. We’re working to get Whisperfish to behave the same (and to support importing the .db after re-registration as well)

4 Likes
1349

Okay

A friend of mine has the Problem that whisperfish stays red and wouldnt connnect anymore.

I think backup .conf and .local is a option if evtl. later is possible to get conversations back?

New registering makes whisperfish working again now, but without old conversations? right?

1350

Group membership seems to be preserved after re-registration, even in cases where I was added to a group during the “blackout”. Messages during that time slot seem lost.

2 Likes
1351

Yes and yes. I still haven’t found time and energy to actually implement the import for the database, but it should come soon™.

4 Likes
1352

Since a few days my WF won’t connect. I’m on Tampella 5.0.0.62 and did no updates.
May it be a connection between the last posts here and the connection-problem?
thanks for help.

1353

That is a yes.

1 Like
1354

Thanks a lot. Ok, but how to do? The option “reconnect” from the pulley is obviously not the right step.
Should i reinstall the app? Or is there a possibility through the Desktop-Signal?

1355

Following this will advise what to do…

2 Likes
1356

Thx. I read this already but wasn’t aware that only moving the directories do the trick to start a new registratin.
Will try this this evening.

1357

I tried the procedure with moving the folders away and re-registering as primary device. However, after solving the hCaptcha I am getting “the address wasn’t understood” in the browser-view. I saw a similar issue in a post here in Feb 2023 but with a much older version of WF. Anyone else experiencing this? I am trying as primary device so that I can keep the history in the linked SD.