Whatly: descargar versiones anteriores

A small fix release for the interface language picker, contributed by gbmaizol (#120).

## What's changed

• **English can be chosen as the interface language.** The picker lists the compiled translations, and English has none because it is the language the interface is written in, so it never appeared：thirty languages, none of them English. On a system set to English, "System default" already gave English, but on a system in any other language there was no way to pick it, and no way back to English once a translation had been chosen. English is now in the list, in its own place, and selecting it simply loads no translation.

Thanks to gbmaizol for the fix and the test.

## Install

• **Linux (portable):** download the `.AppImage`, `chmod +x` it and run. It can update itself in place, verifying each update's signature.
• **Linux (packages):** `.deb` and `.rpm` are attached; Flatpak, Snap and AUR follow through their channels.
• **Windows:** the `.exe`/`.msi` installer, plus a small `.msp` patch to update an existing 7.6.x install.
• **macOS** *(experimental)*：an unsigned `.dmg`; first launch needs right-click -> *Open*.

The AppImage is GPG-signed; the public key (`whatly-appimage-pubkey.asc`) is published alongside the release, and Whatly verifies the signature itself before applying a self-update. Details in [packaging/appimage/SIGNING.md](https://github.com/shakaran/whatly/blob/main/packaging/appimage/SIGNING.md).

Whatly is a desktop wrapper around WhatsApp Web and is not affiliated with, endorsed by, or connected to WhatsApp or Meta.

A small fix release for the collapsed chat list, both fixes contributed by gbmaizol (#117).

## What's changed

• **WhatsApp's "Refresh to update" notice is tamed whenever it appears, not only when the list is collapsed by hand.** Since 7.5.0 the collapsed list treats that notice as the topmost chat, so it is clipped like a row instead of wrapping into a ladder of single letters down the strip. But the notice was only picked up when the list was collapsed or rebuilt, and in practice it arrives on WhatsApp's own schedule：the app is open, the list is already collapsed, and WhatsApp's service worker finds a new version. Nothing looked for it until a manual expand and collapse. It is now checked once a second, which is cheap because it reads two elements and measures no layout.
• **The collapsed chat list no longer mistakes the filter row for an update notice.** When no notice is in the page, the element above the list is the filter row, and it passed every test the fallback detection applied. It was clipped and made clickable as if it were a notice. The fallback now refuses anything holding the filter controls.

Thanks to gbmaizol for the diagnosis, the fixes and the tests.

## Install

• **Linux (portable):** download the `.AppImage`, `chmod +x` it and run. It can update itself in place, verifying each update's signature.
• **Linux (packages):** `.deb` and `.rpm` are attached; Flatpak, Snap and AUR follow through their channels.
• **Windows:** the `.exe`/`.msi` installer, plus a small `.msp` patch to update an existing 7.6.x install.
• **macOS** *(experimental)*：an unsigned `.dmg`; first launch needs right-click -> *Open*.

The AppImage is GPG-signed; the public key (`whatly-appimage-pubkey.asc`) is published alongside the release, and Whatly verifies the signature itself before applying a self-update. Details in [packaging/appimage/SIGNING.md](https://github.com/shakaran/whatly/blob/main/packaging/appimage/SIGNING.md).

Whatly is a desktop wrapper around WhatsApp Web and is not affiliated with, endorsed by, or connected to WhatsApp or Meta.

A tray-icon polish release, following up on the taskbar work in 7.6.3.

## What's changed

• **The colour tray icon is sharp on HiDPI too (#112).** The tray's colour icon was drawn from a 64px raster, so a HiDPI tray or panel that asked for a larger size upscaled it to a blur. Only the monochrome icon stayed crisp, because it is drawn from the SVG, as Nigel1992 noted. The colour icon is now rendered from the scalable app logo as well, and the tray composes it at up to 256px, so it stays crisp at any size. The count badge, previously baked into the 1-9 artwork, is now drawn at every count to match.
• **Optional red unread count on the monochrome tray icon (#112).** A new setting, *Red count on the monochrome icon* (Settings -> Appearance, under the monochrome tray option), draws the unread number in red on the otherwise colourless monochrome icon so it stands out. Off by default, keeping the count the same neutral tone as the glyph. Requested by Nigel1992. The new strings are translated into all 30 interface languages.

## Install

• **Linux (portable):** download the `.AppImage`, `chmod +x` it and run. It can update itself in place, verifying each update's signature.
• **Linux (packages):** `.deb` and `.rpm` are attached; Flatpak, Snap and AUR follow through their channels.
• **Windows:** the `.exe`/`.msi` installer, plus a small `.msp` patch to update an existing 7.6.x install.
• **macOS** *(experimental)*：an unsigned `.dmg`; first launch needs right-click -> *Open*.

The AppImage is GPG-signed; the public key (`whatly-appimage-pubkey.asc`) is published alongside the release, and Whatly verifies the signature itself before applying a self-update. Details in [packaging/appimage/SIGNING.md](https://github.com/shakaran/whatly/blob/main/packaging/appimage/SIGNING.md).

Whatly is a desktop wrapper around WhatsApp Web and is not affiliated with, endorsed by, or connected to WhatsApp or Meta.

• **Settings are no longer lost on every launch.** The Chromium flags are assembled before `main()` sets the application and organization names, and assembling them now reads a setting — the custom-frame check added in 7.6.0 for the frameless-window scroll fix (#104). That first read is what constructs `SettingsManager`, a function-local static that takes both names once, when it is built, so the whole run pointed at an unnamed store：every read returned its default (light window theme, "follow system theme" off, so the system was never consulted either, and no saved accounts) and every write was discarded. The names are now set before anything reads a setting. Nothing was ever written to the wrong place, so an existing configuration comes back untouched.
• **The same fix is expected to resolve the 100% CPU hang on restart (#98),** whose `perf` profile pointed at the settings and single-instance startup path (`QSettings`, `QSharedMemory::attach`) rather than the process spawn：the single-instance shared memory is keyed on the application name, which is now set before it is created.

• **"Link with phone number" can be made to work again (#43).** WhatsApp's phone-number linking refuses to issue a pairing code unless the browser it is told about is one it recognises, and the "Identify as Whatly in linked devices" feature reported an unknown "Whatly", which silently broke that flow while QR linking kept working. The browser name is now a setting：leave it empty for the clean "Whatly" label as before, or set a recognised browser such as Chrome to make phone-number linking work (the browser prefix then reappears in the label). Thanks to Nigel1992 for the precise A/B diagnosis.
• **The Flatpak build moves off the end-of-life KDE 6.9 runtime (#111).** It now targets the KDE 6.10 runtime (Qt 6.10), which matches Whatly's default Qt floor, so the previous `-DQT_VERSION_MINOR=9` override is dropped. Both the local and Flathub manifests are updated.
• **"Find in chats" is now reachable from the command palette.** The `Ctrl+F` chat-list search was already there; it now also appears in the `Ctrl+K` command palette, so it can be reached by name like any other command.
• **A global "boss key" hides every window at once.** `Ctrl+Alt+H` hides all Whatly windows immediately and suppresses message popups while hidden, so nothing surfaces after the hide; pressing it again (or the existing `Ctrl+Alt+W`, or the tray) brings them back and re-enables popups. Unread badges keep updating meanwhile. Where the desktop does not allow an app to register global shortcuts, it registers nothing, the same as the existing raise and quick-compose ones.
• **The restart no longer risks wedging the new instance at 100% CPU (#98).** "Restart now" (after a setting that needs a restart, or a self-update) spawned the new instance by `fork()`-ing the running process, but a QtWebEngine (Chromium) process is not fork-safe：on some setups, an AppImage on Wayland among them, the new instance could spin on a single core indefinitely and had to be killed. It now uses `posix_spawn` instead, which starts a fresh process that execs at once without cloning Chromium's threads and locks, keeping the same new-session detach and the stdout/stderr the log needs (#62). A libc too old for `posix_spawn`'s session and descriptor controls keeps the previous fork-based path.
• **The AppImage self-update now verifies the new image's signature before restarting into it (#85).** 7.5.0 ships a signed AppImage; the updater now checks it. After `appimageupdatetool` writes the new image, Whatly recomputes the signed digest (the image with its `.sha256_sig` and `.sig_key` sections zeroed, SHA-256, hex) and verifies the embedded signature against the signing key compiled into this build (the committed `whatly-appimage-pubkey.asc`, never the incoming image's own key, so a swapped key cannot pass). A tampered image is rejected and the previous version is rolled back from the `.zs-old` backup, with no restart. An unsigned image (older releases) is still applied as before, and a signed one that cannot be checked (no gpg on the system) is applied only with the restart prompt saying so plainly.

• **Test coverage raised to ~90%.** New headless suites drive the parts the pure-logic tests could not reach：the network clients (Ollama check/pull, the translator and the AI assistant) against a stand-in HTTP server, including their no-endpoint, empty-input, malformed-reply and network-error paths; the dictionary catalogue fetch and asset download, the Cloud API send path (text/template/media, with their API-error, network-error and unconfigured branches), and the update check (available/up-to-date/malformed/network-error), each pointed at a local stand-in through an env override; the local API server end to end over loopback (auth, routing, `/send`, and the `/webhook` GET handshake and POST delivery/signature); the widgets offscreen — the command palette, the account tab bar as click and drop target, and the dictionary-row delegate across its states; the tar-based profile export/import and its error paths; the drop reader and resolver; scheduled-message due-checking, recurrence and persistence; session-backup startup recovery; chat-export formatting; the About dialog's toggle and key handling; and assorted `Utils` helpers. What little stays uncovered is code a headless CI cannot exercise — the D-Bus notification and portal paths, the tear-off drag, and GUI-only branches.
• **The Cloud API host and the update-check URL can be overridden by an environment variable.** `WHATLY_CLOUD_API_BASE` replaces the Graph API host and `WHATLY_UPDATE_URL` the GitHub releases endpoint (as `WHATLY_DICT_BASE_URL` already does for the dictionary catalogue). Both default to the real service when unset; they exist so the network paths can be pointed at a local stand-in for testing, and incidentally let an advanced user route through a proxy.
• **Codecov coverage reporting.** A coverage workflow builds the unit suites instrumented for gcov, runs them headless, and uploads a Cobertura report to Codecov; a badge in the README tracks it. (Coverage reflects the CI-safe headless suites — the pure logic in `src/` plus the offscreen widget and network-client tests — not WhatsApp Web itself.)
• **OpenSSF Scorecard.** A weekly workflow audits the repository's supply-chain security posture and publishes the result; the score is shown as a badge in the README and its detail at scorecard.dev, with findings also in the code-scanning tab.
• **No more "OpenType support missing for Noto Sans" log spam.** The language picker lists each language by its native name, so Qt renders scripts the default sans family does not itself carry (Devanagari, Bengali, Arabic…) and logged a warning per script — even though it composes them correctly from the per-script Noto families (fallback working as designed). That one category is now quieted, appended to any `QT_LOGGING_RULES` the user already set.
• **The NVIDIA-on-Wayland fix no longer forces XCB on setups where Wayland works (#84).** 7.3.0 switched every proprietary-NVIDIA Wayland session to XCB up front to avoid a blank window, but on a Wayland setup that renders fine that sent it onto XWayland, where the NVIDIA GL stack could crash the renderer in a loop. Whatly now stays on Wayland and only relaunches on XCB once, automatically, if the backing store actually fails to get a renderer — so the blank-window case is still covered and a working Wayland session is left alone.
• **The "storage bucket persistence denied" console error is gone.** WhatsApp Web moved to the Storage Buckets API, which the existing `navigator.storage.persist()` override did not cover, so the persistence grant Whatly fakes for the classic API was denied for the new one. The override now also wraps `navigator.storageBuckets.open()` so a bucket reports itself persisted.
• **The Windows/macOS codec notice no longer points at a package that does not exist (#93).** When a build without the proprietary H.264 codecs meets an MP4, the notice named "a distro/native package built with the codecs" — but off Linux there is no Flatpak and no codec-enabled build of

Group invite links now open (#186). Clicking a chat.whatsapp.com group invite
(which reaches the app as a whatsapp://chat?code=… link) used to do nothing.
Whatly now opens WhatsApp Web's own "Join group" preview for it, so the invite
can be accepted from the desktop app.

A sound for new-message notifications (#120). Notifications now ask the
desktop's notification service to play its new-message sound, which some setups
stayed silent without. It is on by default and can be turned off under
Notifications with the new "Play sound" option.

Voice and video calls now open in their own Whatly window. WhatsApp Web's
"Move to new window" during a call (the call popout) used to do nothing：the
window request was handed to the browser or discarded, so the popped-out call had
nowhere to live. Whatly now hosts that popout in a proper Whatly window, with the
microphone, camera and screen-share permissions it needs, and closes it when the
call ends. Genuine external links still open in your browser as before. Voice and
video calls themselves work out of the box (#106, #43, #287, #112, #218, #187).

Each account tab shows its WhatsApp Web version. Hovering an account tab now
lists the WhatsApp Web version in use and the page build token, so a mismatch
between accounts is visible at a glance. The tooltip is translated into all
sixteen languages.

Group invite links now open (#186). Clicking a chat.whatsapp.com group invite
(which reaches the app as a whatsapp://chat?code=… link) used to do nothing.
Whatly now opens WhatsApp Web's own "Join group" preview for it, so the invite
can be accepted from the desktop app.

A sound for new-message notifications (#120). Notifications now ask the
desktop's notification service to play its new-message sound, which some setups
stayed silent without. It is on by default and can be turned off under
Notifications with the new "Play sound" option.

Voice and video calls now open in their own Whatly window. WhatsApp Web's
"Move to new window" during a call (the call popout) used to do nothing: the
window request was handed to the browser or discarded, so the popped-out call had
nowhere to live. Whatly now hosts that popout in a proper Whatly window, with the
microphone, camera and screen-share permissions it needs, and closes it when the
call ends. Genuine external links still open in your browser as before. Voice and
video calls themselves work out of the box (#106, #43, #287, #112, #218, #187).

Each account tab shows its WhatsApp Web version. Hovering an account tab now
lists the WhatsApp Web version in use and the page build token, so a mismatch
between accounts is visible at a glance. The tooltip is translated into all
sixteen languages.