0.16.6

The flicker.

The conversation no longer jumps when you send

Your message was briefly drawn twice.

Jackdaw puts your message on screen the instant you press Send, so it never
looks like it was lost while Signal is working. Signal then confirms it, and
the app swaps its own placeholder for the real thing — but the two arrived
six milliseconds apart, and for those six milliseconds both were on screen.

Because the conversation is pinned to the bottom, one extra message does not
just add a row: it moves the view as well. Everything on screen jumps up by a
message's height and drops back again.

Six milliseconds is a fraction of a frame, so whether you saw it came down to
timing — often on a fast monitor, and almost never in a screen recording,
which is why recording it came back clean.

The swap now happens in a single redraw. There is no moment when both exist.

---

Unsigned build. Windows SmartScreen will warn on first run:
choose More info -> Run anyway.

Nothing else to install. The Signal tab drives a real
signal-cli process, and both it and the Java runtime it needs ship
inside the app -- so Signal works on a machine that has neither.
That is most of the download size.

Signal links this machine as a secondary device by QR. As with every
linked device, existing conversations do not arrive by linking: the
tab starts empty and fills as messages arrive, and contacts and groups
do sync. To bring older messages over, use Import history from a
phone in the Signal sidebar, which reads a backup made in Signal on
the phone.

Linux: install the .deb on Debian or Ubuntu -- it is the one
most people want, and unlike the AppImage it does not need libfuse2,
which Ubuntu has not shipped by default since 22.04. The rpm and
pacman packages are built on Ubuntu but target Fedora and Arch. The
AppImage suits anything else, given libfuse2.