v1.9.0

Setting Signal up used to take three runs of the installer, four things installed
beforehand, and a QR code drawn by a tool the script never checked you had. Most of that
is gone.

It is one run now. What it needs is checked before anything happens and handed back as a
single apt install line, rather than discovered one piece at a time — the last of which
used to announce itself only after signal-cli was already installed. It offers to link
this computer to your Signal account where you stand, draws that QR itself, waits for you
to scan it, and then carries on and finishes. Registering is still only explained, never
done for you: it makes the computer become the account and ends Signal on your phone for
that number, which is not a thing to do behind a yes-or-no prompt.

Go is no longer among the things you need. The bridge is built here and published with the
release, and the installer fetches it, checking it against the checksum published beside
it, when Go is absent. Where Go is present it still builds from the source you cloned,
which is the better answer and the reason the download says plainly what it does and does
not prove.

Pairing the phone no longer goes through a browser. Two thirds of the pairing link is a
certificate fingerprint, and that single fact was why you had to pair a browser to the
phone first, purely to have somewhere to paste 140 characters. The installer draws the
link as a QR and Connect a bridge has a Scan button. Point the phone at the terminal. The
paste path is untouched for anyone already in Desktop Sync.

The installer also learned the difference between an operating system and a processor. It
would have told a Mac there was no Signal library for it, which is untrue — macOS is fine,
on both Intel and Apple Silicon. What macOS and Windows lack is systemd, which is a
different problem with a different answer. It says which one is in the way, and says it
before asking for sudo.

Full Changelog: v1.8.1...v1.9.0