Looks like it won’t be too long.
Thanks
EDIT: I might add this is just since upgrade to 5.1.0.8 from 5.1.0.7
Before that I was connecting no problem.
1 Like
Seems like Whisperfish broke for me last night. I’ve identified at least one issue of a protocol change we kinda implemented but apparently not fully. On it…
EDIT: I advice not to start Whisperfish until you install the next version. Every restart will lose you one message.
21 Likes
Can confirm this. Most of the time it is just offline…
2 Likes
Same here, since today morning, Whisperfish doesn’t connect anymore
3 Likes
I can confirm: WF doesn’t get any new messages
1 Like
Confirm Whisperfish cant connect anymore
A good indicator is when the android signal updater gives a notify about a mandatory update. So you know whisperfish need work too.
It would be helpful if the Signal team notified other developers beforehand.
2 Likes
I was contemplating the same thing, but then watching the github with some automated watcher? yesterday there’s been some push here? GitHub - signalapp/libsignal: Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible. · GitHub
However, I cannot imagine that Rubdos hasn’t been watching that one?
Whisperfish 0.6.0-beta.41
[ placeholder for changelog; among others, Whisperfish connects again, but registration is still broken; good night! ]
22 Likes
Not really. Upstream clients deprecate automatically after three months, independent of features (because they can’t know that there were breaking changes, but Signal keeps backward compat for three months).
This particular change I had noticed, and patched, but I had forgotten one last instance. And since that field was sourced from libsignal (and not from our own libs), I hadn’t flagged it with #[deprecated].
It would. But there’s so much churn… at this point it would probably cost them 0.5FTE to actually maintain good change logs for this.
The actual clue was in Signal-Server, this time. I’m playing with some weekly LLM to check for breaking changes, but I don’t expect very good feedback yet.
That would indeed be a bit naive 
We are four of five people that actively watch repos, communicate, and patch, at this point. Sometimes, something slips through. Today was such a day.
Ideally we have better infra in place to test and analyze, but alas. We’re only humans!
16 Likes
Thank you again for quick fix!
4 Likes
With this issue still present in Beta 41, having to reset my device and lose everyhing is rather frustrating.
Lots of personal chats with friends etc
How is the database importer tool you have mentioned coming along?
Thanks a lot for the fix.
Thats a lot and gives you enough time to follow.
Oh, ok, then forget my statement.
Yes, I agree. But it also assumes that we see the change, and there is a lot of patches, every day.
I do believe that if I get some LLM set-up to intelligently watch the server and client repo commits for changes, it should be easier to follow. But it’s going to take a lot of tuning to filter out the false positives, and to not have any false negatives…
2 Likes
Another thought I’ve been tinkering with is that would it be possible to run automated tests between latest version of signal server and service to give early signs of breaking changes?
These tests could be ran nightly and provide overview of which versions starts to break.
And again: thank you for the fast fix! 
4 Likes
That’s assuming that we can easily start up a “Signal server”, which in practice is a huge farm of different interconnected services and database systems. But that’s something we’re looking at together with Molly, indeed.
2 Likes
It’s not coming along, sadly 
The main reason is, I figured out I don’t really care about my conversation history all that much, and I have most of it on Signal Desktop. Most of the development you see in Whisperfish is out of personal need.
1 Like
Well as the db is in sqlite format, I can extract the text out of it if need be. Unfortunate though
1 Like