Repository navigation
A fix for typing after using the Google Messages tab.
Typing works in every tab again
In 0.18.0, once you had used the Google Messages tab, other tabs, Settings and
the lock screen could not be typed into: Windows went on sending your keys to
the Google Messages page even after you had left it. Now the keyboard goes back
to Jackdaw as soon as Google Messages is hidden, whether you switch tabs, open
Settings or Jackdaw locks. And as a backstop, a key that still reaches the
Google Messages page while it is hidden is ignored, so nothing can be typed into
or sent from it while you cannot see it.
If you typed into another tab in 0.18.0 and nothing appeared, it is worth a
glance at Google Messages' message box for text that ended up there.
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.