Whisperfish 0.6.0-beta.17
Sealed sending release, soon near an OpenRepos near you! Sealed sending is a feature in Signal (since 2018 already…) which allows a client to not identify with the Signal servers when delivering a message. This means that Signal LLC does not know who you are when sending a message. Signal enforces this mode of delivery since a few months, and they’ve put a rate limiter on the old method of delivery. This meant that sometimes Whisperfish failed to deliver messages for 24 hours, and this release fixes that issue. I talked about this feature in Lausanne, if you’re interested to see how this works.
In practice, this means two things: one, a huge win for your privacy. Second, fewer (no) failed message sending any more.
There are a lot of other useful changes in this release too!
Changes
- Fixes the profile page not loading
- Fix multiple settings page and profile page issues
- Implement automatic identity key reset
- Implement draft messages
- Fix captcha display and submission
- Ignore NullMessages and implement PlaintexContent
- Implement sealed sending
- Cleaner logging thanks to minimized Display implementations for database types
- Log Qt and QML via simplelog
- Keep identity key in memory, instead of reading from storage
- Stop trying to send messages to unregistered users, store registration state in db
- Consider empty sessions as read, fixes incorrect unread message count
- Expose logging settings in Settings page
- Bump emoji.js
Notes
Log files accumulate, mind their size!
Call for translations
We have been calling Whisperfish “beta” software ever since I started working on it in November 2022. With sealed sending and automatic identity key reset out of the way, we’re trying to move towards a real release. There is still quite some work to be done, but we’re inching closer every day now. We’re planning such a release in the 0.6.0-rc.1 release candidate milestone.
The 0.6.0 release will also hit the Jolla store, and we would love to have the translations up-to-speed when that happens.
As you can see, many translations have been started, but not all of them are maintained perfectly. @direc85 keeps the Finnish up-to-date, I take Dutch, and many other people took the 1300+ words upon them to translate.
What I want to convey here: if you have a few minutes of time, it would be really cool if you could help a bit on Weblate with a language that you know well. If you have questions about a translation string, feel free to ask me!