0.16.4

The flicker, found and fixed — and Microsoft Teams.

The chat area no longer flickers when you send, receive or edit

The controls beside a message — reply, copy, react, delete — were
disappearing whenever the conversation redrew.

They are shown while the pointer is resting on a message. That is something
the browser keeps track of, and it throws it away whenever the row is taken
out of the page and put back, which is what redrawing the conversation does
to any row that moved. Your pointer has not moved, so nothing gives it back:
the controls fade out and stay gone until you move the mouse again.

Measured with a pointer resting on a message: one send, and the controls went
from fully visible to invisible twenty-six milliseconds later, and never came
back — one change in six hundred and seventy-four frames.

Jackdaw now keeps track of this itself, so the controls stay where they are
through a redraw.

Two earlier attempts at this flicker were aimed at the wrong thing. They did
make the conversation redraw far less — of ten rows in the list, none used to
survive an update that changed nothing, and all ten do now — but that was
never what you were seeing.

Switching tabs no longer makes the page jump

A tab being switched to shrank by 24 pixels and sprang back a twelfth of a
second later.

That was deliberate, and it has a purpose: some of these services size their
conversation list once, while the tab is still hidden, and get it wrong. A
real size change is what makes them measure again. What was wrong is when it
happened — after the tab was already on screen and settled, so it was 24
pixels of visible jump.

The same nudge is now spent as the tab appears, when its whole content is
changing anyway.

Microsoft Teams

Teams can be added from the + menu or Settings → Accounts. Work, school
and personal Microsoft accounts all sign in through the same page.

If your organisation's sign-in is federated or behind conditional access, it
may refuse an embedded browser outright. That is the identity provider's
policy and not something this app can work around — the same caveat Slack
carries. Verified as far as the sign-in page rendering correctly, which is the
thing most likely to fail; it has not been signed into and used in anger.

---

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.