0.16.5

The last of the flicker.

The controls beside a message no longer fade in

0.16.4 stopped them disappearing when the conversation redrew. They were
still fading in afterwards, over a tenth of a second, which is the little
blink that was left.

The reason is narrow. A row that is redrawn from scratch — which is what
happens to your own message each time its tick changes from sending, to sent,
to received — came back without the app's note that your pointer was resting
on it. The note was put back immediately afterwards, but putting it back
after the fact is a change, and a change is what the fade runs on.

The note is now carried onto the row as it is rebuilt, so there is nothing to
fade from.

That is the row this matters for: watching your own message as its tick
changes is exactly when the pointer is sitting on the row being redrawn.

---

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.