-
DinoX v2.3.8
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 1m26sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 12m12sBuild / Build AppImage (push) Successful in 35m51sBuild / Build Flatpak (push) Successful in 10m6sreleased this
2026-11-14 12:39:48 +01:00 | 13 commits to master since this releaseDinoX v2.3.8
Choose your Linux or Windows download
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
.deb, AppImage or Flatpak. - Windows 10/11 (64-bit Intel/AMD): download the Windows ZIP, extract it and run
dinox.exe. - Debian 13 (Trixie), Fedora, openSUSE and Arch (64-bit Intel/AMD): use AppImage or Flatpak. The Ubuntu-built
.debrequires different system libraries. - Missing
libgpgme11t64orlibicu74? Check the supported system first. Development (-dev) packages do not fix a binary compatibility mismatch.
What's New
Added
- Download storage limits: Preferences → General → Downloaded Files now offers optional age and size limits, plus a button to clean up files immediately. Both limits are off by default. Cleanup removes eligible received files from DinoX's local storage; messages remain, and a removed file is downloaded again only when requested. Sent files, files currently being played or exported, and copies saved outside DinoX are preserved.
- Quit DinoX: the application menu now includes a Quit command, alongside the existing keyboard shortcut and tray action.
- Empty-input warning sound: pressing Backspace in an empty chat input is silent by default on Windows and Linux. The system warning sound can be enabled in General preferences, independently of message notification sounds.
- Rejoin a disconnected group: the chat offers an account-specific Join again action when a room can be rejoined. The action disappears after a successful join and complements automatic recovery after temporary room-service interruptions.
Changed
- Video playback: playback controls sit below the picture instead of covering it. Videos can be enlarged before or during playback, and can still be played directly in the chat. Enlarging a video leaves the chat row's size unchanged. Audio and video time labels retain compact numeric widths across interface languages.
- Long chat input: the text field grows to 180 logical pixels, then scrolls internally. Text being composed with an input method is laid out before drawing, preserving composition and avoiding invalid scrollbar allocation during input.
- Attachment hover: moving the pointer over an attachment no longer opens an automatic filename, type and size popup. Accessible descriptions remain available.
- Mention markers: the highlight bar now sits to the left of the avatar, leaving more space around the message text.
- Group invitations: public and password-only rooms retain direct JID and invitation-reason entry. Private-room invitations use a stable dialog with direct JID entry, completion from the selected account's contact JIDs, and an invitation reason. Adding an unknown contact ends with a clear confirmation to wait for approval and invite again; it does not silently send the invitation or claim that OMEMO keys have been verified.
- Contact requests: adding a contact normally also shows the actual request outcome and a close button. Long errors remain scrollable without hiding the dialog actions.
Fixed
- YouTube link previews: video links now use YouTube's compact oEmbed metadata instead of relying on titles buried in its full webpage. Regular video links have a landscape preview; Shorts links use a 216 × 384 portrait preview. Image and text space is reserved before loading to keep the chat stable during delayed responses and reopening. Clicking opens the original link in the browser; an inline web player is documented separately and is not included in this release.
- YouTube preview errors: distinguish private/unavailable content, denied preview access, connection and TLS failures, timeouts, rate limits, server failures and invalid responses. Thumbnail failures retain the title and channel, with a separate image notice. An unavailable response is never presented as proof that a video was deleted. Preview requests stay anonymous; videos requiring sign-in open only in the external browser after a click. DinoX does not import browser cookies or sign-in sessions.
- Loading OMEMO keys from other clients: DinoX now accepts valid legacy key bundles whose signed pre-key or one-time pre-key is numbered
0. Previously, DinoX rejected those bundles even when the server supplied them, leaving the keys unavailable and the encryption indicator yellow. Signature checks and existing verification decisions are preserved; no device deletion is needed for this fix. - Removing own OMEMO devices: removal now survives going offline or restarting. DinoX waits for the server to confirm the updated device list and removal of that device's published keys. Pending work stays visible and remains separate for each account.
- OMEMO keys unavailable in DinoX: server-listed devices without a locally available key are now shown with a retry button. Previously, these hidden entries could keep the encryption indicator yellow even when every visible device had been verified. The message describes DinoX's local state; it does not mean that the server has no key.
- OMEMO after joining a private group: discovering room properties or receiving member/owner presence now refreshes encryption readiness. An invited member or the room creator no longer needs to switch chats or toggle encryption after the other participant joins. A participant outside the contact list still needs accessible keys and the required trust; access denied by the server is not treated as successful key retrieval.
- Account separation in group actions: invitations and contact completion use the room's account. Room administration retains the member, administrator or owner affiliation selected when the chooser was opened, rather than reusing a later dialog selection. Delayed presence, configuration and encryption results cannot update a replacement room session or a different account.
- Passwords and CAPTCHA during group joins: invitation passwords survive verification retries and are retained when legacy bookmarks are saved. Joining an existing room stays distinct from creating a new room, including password-protected and members-only rooms.
- Destroyed rooms: normal and automatic joins first check whether the room exists. A stale bookmark no longer silently proceeds as an intentional room creation. Unexpected creation replies are rejected before activating the room; late configuration replies after destruction cannot revive its local state. Failed discovery keeps bookmarks and history. The existence check and join are separate server operations, so a server-side race cannot be made atomic by the client.
- Group-server recovery: temporary service shutdowns and connection errors now retain a retryable room join, even when the account's main XMPP connection stays online. Recovery stops on explicit leave or destruction and does not treat a ban or membership denial as a temporary outage.
- Group disconnection messages: shutdown and connection-error notices say that the connection was lost, without implying that membership was removed. The server's original shutdown text remains available separately. Participant actions distinguish a disconnected room, an offline participant and changed room state; they no longer claim that an offline participant has lost membership.
- Incoming contact requests: requests appear in the receiving account's direct chat with Accept / Reject, even if that conversation was not already open or desktop notifications are disabled.
- Default group avatars: rooms without an uploaded picture keep a stable room placeholder instead of changing to a participant's avatar. Uploaded room pictures retain their normal handling.
- Opening the group list: already decoded room avatars appear immediately when reused. Images that still need reading or decoding load in the background, with account separation and the existing image-size limits preserved.
- Disabling the last account: the main window returns to No active accounts with Manage accounts, instead of leaving an empty chat list. Preferences read the enabled state from the same account instance edited by the settings pages.
- Video-call negotiation with Monal: DinoX now reads Monal's H.264 settings correctly instead of answering with an incompatible video profile and packet format. Translating between Jingle and WebRTC preserves audio/video source attributes and the relationship between video and retransmission streams.
- XML attribute values: tabs and line breaks in attributes now survive parsing by other clients without becoming spaces. Unicode text retains its original value.
- Incoming calls on multiple devices: DinoX now tells the caller that it is ringing when the call invitation arrives as a server-forwarded copy for another logged-in device. Previously, this acknowledgment was missing on that delivery path.
- Ringtone after a network change: a current incoming call can now ring even when it arrives a few seconds late, for example after the caller switches from Wi-Fi to mobile data. Previously, DinoX treated it as a historical call and showed it without a ringtone. Archive entries remain silent.
- Windows voice and video messages: audio recording uses the Windows AAC encoder's supported 96-kbit/s baseline instead of the unsupported 64-kbit/s request. Failed video writers retain their original error and finish cleanup on their owning thread.
- Downloaded videos: completed downloads reuse their local files when a chat is reopened, including after a restart. Generating a thumbnail releases the temporary decrypted video file as soon as it is no longer needed.
- Deleting attachments: deleting a message, conversation or account now also schedules its local attachment files for removal. Files still used elsewhere are kept. If Windows temporarily locks a file, DinoX remembers the deletion and retries later, including after a restart. Cancelled transfers cannot recreate deleted attachments.
- Unicode filenames and stored numbers: non-ASCII filename bytes are no longer mistaken for control characters and replaced with underscores. File sizes, reaction timestamps, certificate dates and OpenPGP publication timestamps retain their full 64-bit values in the Windows database path. Temporary decrypted-file names are shorter while keeping their exclusive directories.
- Pasting Windows screenshots: DinoX tries the clipboard's available image representations individually, so an unreadable bitmap no longer hides a valid PNG or another usable format. A delayed paste remains bound to its original account and conversation and is cancelled when that target changes.
- Chat and member search: searches now use consistent Unicode normalization and case matching. Short member names such as "im" can be found, and member ordering is the same on Windows and Linux. Current-chat searches stay within the selected conversation and account.
- Unexpected chat scrolling: adding a reaction or closing search with Escape no longer moves the chat into older messages in the reproduced Windows cases. Escape also closes member search, and clicking visible messages preserves the current position.
- Opening preferences: settings pages are created when selected. Opening the Accounts page no longer prepares all the other settings pages first.
- Network status overview: changing Tor or connection status keeps the open overview at a stable width. Long status messages wrap, and long account lists remain scrollable.
- Preparing audio and video attachments: reading a file's duration now runs in the background, so a slow decoder or file read no longer blocks the chat interface. Preparing several files uses at most two metadata workers.
- MQTT history and Unicode: history and charts stay within the selected broker connection, both in the database and in memory, even when brokers use identical topic names. Shortened payload previews retain valid UTF-8. Windows certificate lookup uses DinoX's package directory rather than an unrelated working directory or old MSYS2 installation.
- Botmother and API boundaries: deleting a bot removes its stored OMEMO state even when the plugin is disabled. API address validation accepts valid Unicode bytes while rejecting invalid UTF-8 and control characters. Long translated webhook actions fit within the dialog.
- OpenPGP state: an unchanged, previously verified legacy presence announcement keeps its key available while its signature is checked again. Changed or invalid announcements still lose that state. Publication lookups correctly distinguish an absent database row, and Windows key inspection uses the same bundled-first GnuPG resolver as other operations.
- Windows notification-sound lifecycle: unloading or registering the plugin again disconnects its old event handlers, so later events cannot restart stopped playback or accumulate duplicate handlers.
Builds and desktop integration
- Windows UCRT64 baseline: build scripts now use a pinned UCRT64 toolchain instead of MINGW64. The packaged GTK, Pango and libadwaita corrections cover native input-context cleanup, animated SVG clock handling, color-emoji font selection, missing-glyph fallback and translated alert-heading measurement. The accepted runtime remains separate from unpromoted input-method experiments.
- Reproducible and public Windows builds: German and English instructions distinguish reusing the maintainer's fixed private build packages from a public source build using current MSYS2 UCRT64 packages. Public builds do not require the private SDK archives and may use newer dependencies. Preparation and packaging write logs and report the actual failing command.
- Refreshed call runtime: Linux and Windows package inputs pin the rebuilt Google/libwebrtc M152 ABI 40 / IPC 10 runtime, including separate receive and remote sender-report diagnostics. Normal DinoX builds reuse these archives rather than rebuilding WebRTC each time.
- AppImage taskbar icon: the launcher registers a persistent per-user desktop entry and icon outside the temporary AppImage mount, allowing desktops to associate the running window with DinoX. The DEB launcher preserves its desktop window class. Flatpak validation checks the installed desktop identity and icon files.
Tests and translations
- Regression coverage now includes private-room readiness, invitations and account separation, destruction/rejoin races, temporary room-service recovery, contact requests, independent hat colors, clipboard fallback, attachment deletion and reuse, Unicode search, scroll position and preview geometry.
- Database and profile tests exercise persistent data across accounts, reopening, removal and backup restoration, including actual OMEMO/OpenPGP message decryption. MQTT, Botmother/API, notification sounds and translated settings/dialogs have focused runtime checks in addition to catalog checks.
- Native Windows checks cover the accepted UCRT64 package, Unicode/TLS paths, image clipboard formats, audio/video writers, database boundaries and the selected translated UI cases. Linux and native Windows YouTube tests cover metadata/image failures, stable layouts and anonymous requests; German and right-to-left layouts are included.
- New interface text is translated across the maintained catalogs. English and all 37 maintained translations are covered by the relevant settings, invitation, recovery or catalog suites. These checks do not claim exhaustive live-server, hardware or input-method testing for every language.
Upgrade notes and known limitations
- Upgrading from 2.3.7 and OMEMO: existing keys and verification decisions are preserved. In the investigated contact-key failure, the server supplied valid keys matching those displayed by Monal. DinoX rejected their key number
0; an incomplete device deletion was not the cause. Restart the updated DinoX and use Retry if the keys are still shown as unavailable. Neither you nor your contact needs to delete devices to resolve this parser error. - Separate own-device removal fix: if the account owner had explicitly requested a removal that 2.3.7 did not retain, that removal must be confirmed again in the owner's device settings. This applies to installations the owner actually wants to remove, not to keys rejected by the parser. The update does not automatically delete devices with unavailable keys. See OMEMO key loading and device removal.
- Input-method candidate windows: actual Chinese input and long-text insertion have been exercised, but a visible candidate row can still wait until the next key after a layout move. DinoX does not install the experimental system IBus-panel patch or the unpromoted Windows GTK candidate. See language testing for the separate platform results.
- Older Windows report: the AAC correction has native Windows 11 before/after evidence; the reporter's Windows 10 LTSB build 14393 remains untested.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.8_amd64.deb.sha256 sudo apt update sudo apt install ./dinox_2.3.8_amd64.debRun in the download folder. APT installs the required runtime dependencies from your configured Ubuntu/Mint repositories.
This package is not a Debian Trixie binary; use AppImage or Flatpak there. Do not force installation or add Ubuntu repositories to Debian.AppImage
sha256sum -c DinoX-2.3.8-x86_64.AppImage.sha256 chmod +x DinoX-2.3.8-x86_64.AppImage ./DinoX-2.3.8-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.8-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.8-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.8.tar.gz.sha256 tar xf dinox-2.3.8.tar.gz cd dinox-2.3.8 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/.vendor-deps/linux-tor-runtime/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
4 downloads
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
-
DinoX v2.3.7
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 3m16sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 1h20m31sBuild / Build AppImage (push) Successful in 2h39m23sBuild / Build Flatpak (push) Successful in 1h51m45sreleased this
2026-11-02 23:19:24 +01:00 | 64 commits to master since this releaseDinoX v2.3.7
Choose your Linux or Windows download
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
.deb, AppImage or Flatpak. - Windows 10/11 (64-bit Intel/AMD): download the Windows ZIP, extract it and run
dinox.exe. - Debian 13 (Trixie), Fedora, openSUSE and Arch (64-bit Intel/AMD): use AppImage or Flatpak. The Ubuntu-built
.debrequires different system libraries. - Missing
libgpgme11t64orlibicu74? Check the supported system first. Development (-dev) packages do not fix a binary compatibility mismatch.
What's New
Added
- Group join verification: groups that require a CAPTCHA now open a verification dialog with the image or question, an answer field and clear retry/cancel controls. Browser links remain available for unsupported challenges. HTTP links show a warning and require confirmation before opening. Room administration offers the CAPTCHA switch when the server supplies it.
Fixed
-
Group-server restarts: a service-shutdown notification no longer closes the chat or removes its saved group bookmark. The disconnected state is shown as information, without claiming that membership was revoked or the room destroyed. Actual access denials and room deletion remain separate.
-
Reaction picker: a background message update no longer cancels a click on Add reaction or briefly hides an open emoji picker.
-
Opening files from the AppImage: external players such as mpv now receive the original desktop library paths. Previously, they could load libraries bundled for DinoX and stop with a missing-symbol error. DinoX keeps its own bundled runtime.
-
Starting calls: audio and video calls now check the contact's current call support without depending on the retired RTP plugin. Previously, a contact missing from the capability cache could not be called from packages such as the AppImage. The call window opens while this check runs, so setup errors are visible and a waiting call can be cancelled.
-
Slow groups with large avatars: very large contact and participant pictures are now processed in the background. DinoX reuses small previews when switching chats or opening member lists, instead of repeatedly decoding the full image and blocking the interface. Linux desktop notifications use these previews too.
-
Groups appearing as contacts: CAPTCHA and other messages from a known room stay with that room. They no longer open a personal chat, show contact approval prompts or turn the verification link into a file download. Existing duplicate sidebar entries are hidden without deleting their history. Accounts remain separate.
-
Small verification dialogs: CAPTCHA actions and long translations wrap within the window. The form remains scrollable, including with Bengali and Hindi text on Windows.
-
Damaged optional previews: truncated avatar and thumbnail data is rejected before Windows image-format probing. This avoids a reproduced decoder error without changing the original attachment.
-
Compact chat list: tooltips return when a row is shown again, even if its text has not changed.
-
Copying text: context menus open after the right mouse button is released, avoiding GTK active-state warnings in chat and dialog fields. Selection, Unicode text and the link under the pointer are preserved.
-
Chat menus: opening or closing header menus no longer moves the chat into older messages.
-
Unicode and reading direction: long room topics no longer end with a broken character. A separate startup error that could corrupt the language setting and select the wrong reading direction has also been corrected.
-
System-language independence: encrypted-file cipher identifiers, raster sticker types, bot provider selection, MQTT playlist tokens and call codec names use stable ASCII case rules. XMPP capability hashes use the required byte ordering instead of system-language sorting.
-
Language regression coverage: catalog loading, settings templates, selected chat/plugin boundaries and Linux tray tests now cover every offered language. Package descriptions use the established Chinese and Brazilian Portuguese language tags.
-
Group-history loading now applies moderated retraction records from the room archive, including records of edited messages. Removed content stays hidden when older revisions arrive later or DinoX restarts; other accounts, rooms and senders remain separate.
-
Messages containing custom emoji markup retain their readable text. Unsupported emoji elements no longer become italic text, and their image resources are not downloaded as ordinary attachments. Other attachments and existing stickers retain their normal handling. Sending and rendering custom image emojis are not implemented.
Tests and documentation
- Regression checks cover reaction clicks during message updates, external AppImage program launches, outgoing call discovery and cancellation, large avatars, failed PNG previews, cancelled notifications, CAPTCHA joins, account separation and copying text. The language matrix includes the new controls and Unicode paths in every offered app language. Desktop notification tests check the actual image data through both the desktop service and portal interfaces.
- Testing documentation now lists the corresponding commands and distinguishes local fixtures, native Windows checks and package/desktop acceptance. Flatpak package validation also checks the notification-service permission.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.7_amd64.deb.sha256 sudo apt update sudo apt install ./dinox_2.3.7_amd64.debRun in the download folder. APT installs the required runtime dependencies from your configured Ubuntu/Mint repositories.
This package is not a Debian Trixie binary; use AppImage or Flatpak there. Do not force installation or add Ubuntu repositories to Debian.AppImage
sha256sum -c DinoX-2.3.7-x86_64.AppImage.sha256 chmod +x DinoX-2.3.7-x86_64.AppImage ./DinoX-2.3.7-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.7-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.7-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.7.tar.gz.sha256 tar xf dinox-2.3.7.tar.gz cd dinox-2.3.7 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/.vendor-deps/linux-tor-runtime/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
22 downloads
-
Source code (TAR.GZ)
5 downloads
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
-
DinoX v2.3.6
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 2m20sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 1h0m38sBuild / Build AppImage (push) Successful in 2h3m28sBuild / Build Flatpak (push) Successful in 1h8m43sreleased this
2026-11-01 13:47:47 +01:00 | 98 commits to master since this releaseDinoX v2.3.6
Modern XMPP client with extended features.
Choose your Linux download
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
.deb, AppImage or Flatpak. - Debian 13 (Trixie), Fedora, Opensuse, Arch: use AppImage or Flatpak. The Ubuntu-built
.debrequires different system libraries.
What's New
Added
- Yue Chinese (Cantonese): the app, settings, dialogs, OMEMO, OpenPGP and package descriptions are available in traditional Cantonese, listed as 粵語. Regional
yue_HKandyue-Hant-HKsettings use the same translation; the existing simplified and traditional Mandarin translations remain separate. - Vietnamese: the app, settings, dialogs, OMEMO, OpenPGP and package descriptions are available in Vietnamese. Previously incorrect translations have been corrected, including connection errors, location actions and MQTT controls. Regional
vi_VNsettings use the same translation. - Egyptian Arabic: the app, settings, dialogs, OMEMO, OpenPGP and package descriptions are available in Egyptian Arabic, separately from Modern Standard Arabic. The interface uses right-to-left layout.
arz_EGuses this translation;ar_EGcontinues to use Modern Standard Arabic. - Nigerian Pidgin: the app, settings, dialogs, OMEMO, OpenPGP and package descriptions are available in Naija Pidgin. Regional
pcm_NGsettings use the same translation.
Fixed
- Tray menus and notifications: Linux menus preserve underscores in status text and follow the selected language's reading direction. DinoX also registers with desktops that expose only the alternate status-notifier watcher and handles watcher restarts and late replies during shutdown. Windows notifications no longer cut an emoji in half at a text limit, and tray logging works with Unicode folder names.
- Language-independent processing: link previews preserve Unicode text when reading HTML metadata; uppercase update hosts, audio protocol parameters and bot commands are handled consistently across system languages. Windows GnuPG paths keep ASCII drive letters without changing Unicode folder names.
- MQTT alerts: JSON numbers retain their precision when compared with thresholds. Decimal-comma system settings no longer prevent matching alerts, and uppercase priority names retain their meaning under Turkish system settings.
- File types in Turkish system locales: uppercase MIME types and extensions such as
VIDEO/MP4,.GIFand.AVIare recognized using language-independent case rules. This keeps media previews and encrypted-file detection consistent across system languages. - Video messages: reopening a chat uses an available preview immediately. Delayed first display now starts preview generation reliably, leaving a chat stops playback and restores its preview, and video dimensions no longer change the message height when the preview or player appears.
- HTTP downloads: timeout and connection errors retain their technical error codes. Automatic retries no longer depend on whether the error message is in English, German or another language.
- AppImage modules: GIO, GTK, GStreamer, image decoders and sound backends use matching libraries from the package. Missing NSS cryptographic modules, OpenSSL modules, proxy settings and fallback sounds are also included. This fixes the reproduced module-loading errors and reduces dependencies on the desktop's installed components. The cause of the reported remote HEAD timeout remains unconfirmed.
- AppImage secure connections: DinoX now loads the system certificate bundle selected by its launcher through GIO's TLS API. This fixes certificate rejection reproduced on openSUSE, where the bundle is stored at a different path from Ubuntu. Certificate and hostname checks remain enabled.
Development
- The
systrayMeson suite checks translated Linux menus, packaged icons and desktop registration through the Flatpak D-Bus policy. Windows tests exercise the native menu, accessibility names, notification queue, Explorer restart and Unicode text limits without registering a real tray icon. - The OpenPGP test target now declares its dependency on the HTTP-files header, so a clean selective Windows test build creates the header before compiling.
- The
locale-boundariesMeson suite exercises real HTML, MIME, update URL, XMPP, bot, MQTT and GnuPG paths under verified German and Turkish system locales. Missing locale data is reported as a skip. These checks complement translated-interface and Unicode media-path tests; they do not assert that every feature has been tested in every language. - The Hats dialog test now waits for completed loading and actual command responses instead of assuming fixed delays are sufficient. Media regression tests also cover Unicode file paths and the separation between interface language and numeric protocol values.
- Windows Qlite builds use the same generated-Vala-code warning settings as the other Vala libraries, excluding unused compiler-generated helpers and labels. Native C warning settings remain unchanged.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.6_amd64.deb.sha256 sudo apt update sudo apt install ./dinox_2.3.6_amd64.debRun in the download folder. APT installs the required runtime dependencies from your configured Ubuntu/Mint repositories.
This package is not a Debian Trixie binary; use AppImage or Flatpak there. Do not force installation or add Ubuntu repositories to Debian.AppImage
sha256sum -c DinoX-2.3.6-x86_64.AppImage.sha256 chmod +x DinoX-2.3.6-x86_64.AppImage ./DinoX-2.3.6-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.6-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.6-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.6.tar.gz.sha256 tar xf dinox-2.3.6.tar.gz cd dinox-2.3.6 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/.vendor-deps/linux-tor-runtime/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
20 downloads
-
Source code (TAR.GZ)
6 downloads
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
-
DinoX v2.3.5
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 2m16sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 1h0m30sBuild / Build AppImage (push) Successful in 1h49m2sBuild / Build Flatpak (push) Successful in 1h6m1sreleased this
2026-10-31 20:42:37 +01:00 | 119 commits to master since this releaseDinoX v2.3.5
Modern XMPP client with extended features.
Choose your Linux download
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
.deb, AppImage or Flatpak. - Debian 13 (Trixie), including SparkyLinux 8.x (64-bit Intel/AMD): use AppImage or Flatpak. The Ubuntu-built
.debrequires different system libraries. - Missing
libgpgme11t64orlibicu74? Check the supported system first. Development (-dev) packages do not fix a binary compatibility mismatch.
What's New
Fixed
- OMEMO after re-enabling an account: fixed a session error that could occur after disabling and re-enabling an account. Old background operations can no longer overwrite the current encryption session. Existing keys and saved sessions are preserved, and other accounts remain unaffected.
- Sending images: reading image dimensions and preparing thumbnails now runs in the background. This step could previously block the interface even after the chat-preview fixes. Invalid or oversized optional previews are skipped without changing the original file or the server's upload size limit.
- Messages from removed contacts: a new message now reopens the chat. Previously, DinoX could show a desktop notification while leaving the conversation hidden. The sender stays outside the contact list, and previously deleted messages remain deleted locally.
- Switching chats: conversation and notification menus are reused instead of being recreated on every switch. The call button updates immediately, so a public group no longer briefly shows the previous chat's phone button. Open menus close when their target changes.
- OMEMO device activity: the hint now explains that this DinoX has not seen the device recently and that the device may still be in use. It no longer labels the device "Stale" or suggests removing it solely because of locally observed inactivity.
Builds and tests
- Windows compiler warnings: unused callback and cleanup warnings in the affected tests and Tor code were corrected in the source. Two OMEMO initialization and backup warnings were also corrected. Further warnings about unused helpers and labels generated by Vala are filtered only for generated OMEMO C code; the handwritten cryptographic helper keeps its existing warning checks. This does not claim that every warning from a full Windows build has been removed.
- Regression coverage: tests now exercise two accounts while one is disabled and re-enabled, reject callbacks holding obsolete OMEMO state, and check menu and call-button updates when switching chats. OpenPGP upload-cancellation tests allow for slow encryption startup and stop cleanly if setup fails.
The image change fixes a demonstrated interface-blocking path. The particular file reported to crash DinoX on Windows was not available for reproduction, so that report is not considered fully resolved by this release.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.5_amd64.deb.sha256 sudo apt update sudo apt install ./dinox_2.3.5_amd64.debRun in the download folder. APT installs the required runtime dependencies from your configured Ubuntu/Mint repositories.
This package is not a Debian Trixie binary; use AppImage or Flatpak there. Do not force installation or add Ubuntu repositories to Debian.AppImage
sha256sum -c DinoX-2.3.5-x86_64.AppImage.sha256 chmod +x DinoX-2.3.5-x86_64.AppImage ./DinoX-2.3.5-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.5-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.5-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.5.tar.gz.sha256 tar xf dinox-2.3.5.tar.gz cd dinox-2.3.5 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/.vendor-deps/linux-tor-runtime/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
19 downloads
-
Source code (TAR.GZ)
1 download
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
-
DinoX v2.3.4
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 2m58sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 58m50sBuild / Build AppImage (push) Successful in 1h49m3sBuild / Build Flatpak (push) Successful in 1h17m18sreleased this
2026-10-31 10:52:46 +01:00 | 131 commits to master since this releaseDinoX v2.3.4
Modern XMPP client with extended features.
Choose your Linux download
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
.deb, AppImage or Flatpak. - Debian 13 (Trixie) use AppImage or Flatpak. The Ubuntu-built
.debrequires different system libraries.
What's New
Added
- Five more languages: Bengali, Indonesian, Hebrew, Urdu and Japanese now cover the app, settings, dialogs, OMEMO, OpenPGP and package descriptions. Hebrew and Urdu use a right-to-left layout. DinoX now offers English and 33 complete translations.
- Ctrl+Enter to send is an optional setting under Preferences → General. When enabled, Enter inserts a new line. The default remains Enter to send and Shift+Enter for a new line. The setting applies immediately to all chats and is saved across restarts.
- Window buttons can follow the system preference or be placed on the left or right. The choice also applies to password prompts and call windows. Windows no longer forces the buttons to the left.
- Attachment menus offer “Copy Link” for files, images, videos and audio messages, including before a download or after a failed download. Hovering over an attachment shows its filename, type and size. This hint stays hidden while the menu is open.
Fixed
- Image previews are decoded in the background and scaled during decoding, including animated GIF frames. Limits on the downloaded data and image dimensions prevent oversized previews from exhausting resources. Damaged images cannot bypass an already detected size limit. Download controls remain available while a preview loads, and hidden download spinners stop their timers.
- Copied encrypted file links now appear as attachments in the sender's chat too. Pasting and sending an
aesgcm://link to a video, image or audio file uses the normal download and preview controls instead of leaving a long address in the chat. - Chat scrolling no longer continues an old message-jump animation after switching conversations. Late link previews keep the message being read in place, whether they appear above or below it. Position adjustments finish before the next frame is drawn.
- Link previews load their images in the background with download size limits. Recently viewed previews stay in the cache. Relative image addresses now retain the original site's port.
- Native GTK and GIO bindings now use the correct pointer types for string lists, clipboard and drag-and-drop reads, and file streams. This removes all 31 incompatible-pointer warnings from the Windows build without changing encryption or file-transfer algorithms.
Builds and documentation
- Windows warning reports now count the entire build, including failed builds, and save a separate
compile-*.warnings.txtfile. A zero count from a later incremental build no longer suggests that earlier compilation was warning-free. The checked full build has 200 remaining warnings, all for unused functions or labels generated by Vala; they have not been hidden. - Build and regression checks now cover the corrected stream bindings, localized cancellation errors and the full warning report. Strict builds also detect C++, header and compiler-driver warnings.
- Windows build instructions now provide separate, ordered paths for a first build, a rebuild of master, a package from an existing release tag and a new release. The overview links directly to each step and explains where the complete logs are saved.
- The website also offers the five new languages on the home page, downloads, provider directory, legal pages and its own community-chat instructions. Guide and chapter contents remain German and English; Converse's own menus use English when Urdu is selected.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.4_amd64.deb.sha256 sudo apt update sudo apt install ./dinox_2.3.4_amd64.debRun in the download folder. APT installs the required runtime dependencies from your configured Ubuntu/Mint repositories.
This package is not a Debian Trixie binary; use AppImage or Flatpak there. Do not force installation or add Ubuntu repositories to Debian.AppImage
sha256sum -c DinoX-2.3.4-x86_64.AppImage.sha256 chmod +x DinoX-2.3.4-x86_64.AppImage ./DinoX-2.3.4-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.4-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.4-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.4.tar.gz.sha256 tar xf dinox-2.3.4.tar.gz cd dinox-2.3.4 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/.vendor-deps/linux-tor-runtime/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
22 downloads
-
Source code (TAR.GZ)
3 downloads
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
-
DinoX v2.3.3
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 9m2sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 55m39sBuild / Build AppImage (push) Successful in 1h44m40sBuild / Build Flatpak (push) Successful in 1h1m5sreleased this
2026-10-29 20:36:21 +01:00 | 155 commits to master since this releaseDinoX v2.3.3
Modern XMPP client with extended features.
Choose your Linux download
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
.deb, AppImage or Flatpak. - **Debian 13 (Trixie), use AppImage or Flatpak. The Ubuntu-built
.debrequires different system libraries.
What's New
Highlights
- New optional appearance: DinoX Design gives the app a green theme, including settings, confirmation and error dialogs, password prompts and call windows. The classic appearance remains available. The mint-green DinoX icon now appears throughout the app and in the system tray.
- 28 complete translations plus English: The translations now cover settings, dialogs and the OMEMO and OpenPGP plugins. Previously missing texts and a fault that loaded outdated translations have been corrected. DinoX uses English when a language is not supported.
- Chat history fixes: “Load messages now” can retrieve available messages again after the local history has been deleted, including in private groups. Previously read and locally deleted OMEMO messages cannot be recovered from the server archive alone; DinoX now explains this once per reload.
- Editable group badges: Group badges, called “Hats” in DinoX, can now be renamed and recolored with a color picker. Existing assignments are preserved, and saving or closing the editor returns to the badge overview.
- AppImage and Windows builds: The AppImage includes a missing component needed for secure connections. Windows builds now save the complete console output to a log file, prevent builds with Administrator rights and have a complete release guide in German and English.
Appearance and group management
- DinoX Design is available under Preferences → General → Appearance. Classic and DinoX Design both work with the System, Light and Dark choices and custom accent colors. Existing profiles keep the classic appearance. High-contrast mode retains the system's accessibility colors.
- The application icon now uses the same mint-green DinoX symbol as the website, including Linux desktop packages, the Windows executable and tray icons. All icon sizes come from the same vector image.
- Conversation menus now have separators between related actions, both in the chat list and in the menu at the top of a conversation.
- Group badges (Hats) can be edited from the list of available badges or from an existing assignment. The color picker shows a live preview. Renaming a badge preserves its custom color, and changing its name or color preserves its assignments. DinoX confirms changes after the server accepts them and updates the overview without closing it. Badge colors support 360 hues with readable text, and the new controls are translated.
- Destroying a room now clears its local joined state, bookmark and record of previously loaded server history after server confirmation. This also works through server administration for rooms the account has not joined, and with servers that omit a normally expected presence marker. Saved messages remain on the device, and a delayed reply cannot undo a newer join. Both confirmation dialogs now explain that destroying a room does not erase messages on participants' devices; removal of the server archive depends on the server's settings.
- Removing a contact and its history now waits for the server to confirm the contact's removal. A rejected request or an outdated reply no longer deletes local messages. The action affects only the selected account and conversation, even when a group, direct chat or private group message uses the same address.
Message history
- Reloading after local deletion works again in direct chats and groups, including after leaving and rejoining a group. DinoX requests the chosen history period from the server. For groups, only the selected room's record of previously loaded history is reset. Automatic synchronization still respects local deletion. Deleting history while a reload is running, message expiry and emergency deletion still prevent those messages from being saved again. The wording now distinguishes local deletion from a request to retract your own messages.
- Private group archives are now assigned to the correct group conversation, even if an old direct-chat entry exists for the same room address. The requested history period and the final reload result therefore belong to the group. If the server reports that no archive is available, DinoX now shows that result, including when the reply arrives late.
- Old OMEMO messages that this device already decrypted cannot be restored from the server archive alone after local deletion. During a manual reload, DinoX reports these unavailable messages in one summary instead of filling the chat with a separate error for each one. Unencrypted messages can be restored while the server still holds them. The completion message now describes the result without promising that every message was recovered.
- New messages and offline delivery continue to use the existing receive and decryption paths for OMEMO, legacy OpenPGP (XEP-0027), modern OpenPGP (XEP-0373/0374) and unencrypted messages. Errors for newly received messages remain visible individually, including after a later manual reload. Existing key checks, duplicate-message protection, account separation and cancellation handling remain in place.
- Optional archive diagnostics record query metadata, local deletion limits and processing steps when explicitly enabled. They are off by default and exclude message contents, credentials and cryptographic session records. Enabling them does not change which messages are recovered or saved.
Languages
- The interface is available in English and 28 complete translations: Arabic (Modern Standard), Bulgarian, Catalan, Chinese (Simplified and Traditional), Czech, Danish, Dutch, Estonian, Finnish, French, German, Hindi, Hungarian, Italian, Latvian, Lithuanian, Norwegian Bokmål, Polish, Portuguese (Portugal and Brazil), Romanian, Russian, Slovak, Spanish, Swedish, Turkish and Ukrainian.
- The translations cover the main application and both encryption plugins, including accounts, DNSSEC/DANE and certificate warnings, account deletion, password prompts, archive recovery, calls, feeds, group badges, server administration, Botmother, MQTT and Tor. Desktop descriptions, software-center descriptions, screenshot captions and release summaries have also been completed. Regional Portuguese terminology and Traditional Chinese terminology were reviewed separately.
- Earlier translation errors have been corrected, including duplicated paragraphs, untranslated warnings, text left in another language and misleading terms for sign-in, contacts, commands, model names, delivery and read status, group roles and permissions, encryption, device trust and key fingerprints. Corrections also cover typing notices, location actions, stickers and backup warnings. German MQTT menu texts were reviewed, and existing German wording was retained as a reference.
- Missing settings and dialog texts are now included. The translation tools previously missed 30 messages, including account setup, proxy fields, search, password entry and plural counts. DinoX now also uses the existing translations for the account password prompt, the automatic language choice and MQTT alert priorities and operators. Stored MQTT rule values are unchanged.
- Bundled translations now load correctly even without a separate English translation file. Local builds previously could fall back silently to older installed translations. Main and plugin translations are now found in the build, portable package or explicitly selected translation directory.
- Language selection offers complete translations only. An unsupported saved or system language falls back to English. Incomplete translation files remain in the source tree for future work. The package checks compare shipped translations with the current source text, including every plural form and formatting placeholder. Hindi plural rules are consistent across all three translation files; Arabic uses its six plural forms.
- Arabic layout now follows the selected app language, even when the system has no Arabic GTK translation installed. Text fields with an explicitly assigned direction retain it. The website also has an Arabic version with right-to-left navigation and page layout.
- Translation and package checks have been extended. Latvian now has the previously missing OMEMO translation, and Slovak and Bulgarian have complete translations and their own language choices. The Flatpak checks include these additions across all three translation domains. Extraction now covers the missing UI and Tor texts, plural messages and UTF-8 plugin strings. Tests check the UI text markers and translation lookup; audio/video tests use translated labels, and the tab-scrolling test no longer depends on the length of a translated title.
Packages and builds
- AppImage secure connections no longer depend on the host having a compatible GIO TLS component. The package now contains the GnuTLS module, its required libraries and its module cache, and the launcher points to them. This fixes the error “TLS support is not available” reported in issue #34. Package checks verify that these files and settings are present.
- Windows build logs now contain the complete normal and error output, including cleanup and test failures. Each build writes a separate log outside the source folder and still returns a failing exit status if the build fails. The script refuses to run with Administrator rights before it starts cleaning, preventing files that a later normal-user build cannot remove. The German and English instructions explain how to recover from earlier Administrator builds.
- The Windows release guide now describes the whole sequence in one place: preparing the version, building the chosen source commit, reviewing logs and manual tests, creating and verifying the ZIP and checksum, tagging the tested source and uploading the package. Package output stays outside the source folder and is separated by version and source commit.
- Temporary Forgejo build artifacts for DEB, AppImage and Flatpak are retained for seven days. This limit does not apply to published release downloads.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.3_amd64.deb.sha256 sudo apt update sudo apt install ./dinox_2.3.3_amd64.debRun in the download folder. APT installs the required runtime dependencies from your configured Ubuntu/Mint repositories.
This package is not a Debian Trixie binary; use AppImage or Flatpak there. Do not force installation or add Ubuntu repositories to Debian.AppImage
sha256sum -c DinoX-2.3.3-x86_64.AppImage.sha256 chmod +x DinoX-2.3.3-x86_64.AppImage ./DinoX-2.3.3-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.3-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.3-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.3.tar.gz.sha256 tar xf dinox-2.3.3.tar.gz cd dinox-2.3.3 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/.vendor-deps/linux-tor-runtime/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
14 downloads
-
Source code (TAR.GZ)
4 downloads
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
-
DinoX v2.3.2
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 1m9sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 1h3m6sBuild / Build AppImage (push) Successful in 1h46m46sBuild / Build Flatpak (push) Successful in 1h2m32sreleased this
2026-10-24 00:07:27 +02:00 | 205 commits to master since this releaseDinoX v2.3.2
Modern XMPP client with extended features.
Choose your Linux download
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
.deb, AppImage or Flatpak. - **Debian 13 use AppImage or Flatpak. The Ubuntu-built
.debrequires different system libraries.
What's New
Changes since 2.3.1. Release preparation and package acceptance are tracked in
Release readiness.Highlights
- Feeds and account security: Read and share web feeds, publish personal XMPP posts, choose DNSSEC/DANE per connection, and see whether additional login protection is available and active.
- More video effects, processed locally: Camera controls now include additional filters and image adjustments, background blur and replacement, automatic framing, and face accessories. The optional person and face detection runs offline and starts only when the selected effect needs it.
- Turn a one-to-one call into a conference: Invite another participant during an ongoing 1:1 audio or video call. DinoX checks group-call support, prepares a private temporary call room and preserves the existing microphone/camera choices. This requires group-capable participants.
- Clearer group-call controls: Start a call in an existing private chat room, join a running call, return to its room, or invite another participant from a one-to-one call. Compact controls keep the video-effects button accessible.
- Easier voice messages and stickers: Recording stays in a popover with a live waveform and explicit Send/Discard actions. Chat audio players are compact, with seeking, playback speed and clearer time labels; sticker imports show progress and animation settings apply to chat previews.
- Account-specific privacy and key management: Profile operations and server administration retain their selected account. OpenPGP key assignment, publication and server-backup cleanup distinguish the selected key from keys used by other accounts.
- Better recovery from stale OMEMO keys: Refreshes the device's published keys after one-time keys are consumed and can repair eligible failed sessions with trusted contacts. The account's device identity and trust decisions are preserved; old messages that require missing private keys remain unreadable.
- Clearer chats and easier history access: Compact message headers, persistent mention markers and improved narrow-window layouts make conversations easier to follow. One-to-one chats and groups can request archived messages directly, with an optional history period for each group.
- Compact chat list and controlled Tor recovery: Collapse the wide-window chat list to small avatars with visible unread and group badges. If Tor or a proxy is unavailable after restart, DinoX stays usable so the route can be changed explicitly; it does not silently connect directly.
Added
- Visible account login protection: A green check confirms usable SCRAM-PLUS protection for the selected account; a red cross identifies unavailable protection. Policy choices remain disabled until availability is confirmed. Changing the selection automatically reconnects that account and reports the result. Connection failures remain distinct from missing support, and existing requirements are never relaxed automatically.
- Feeds in chats and XMPP social posts: Preview and share RSS 1.0, RSS 2.0 and Atom articles through the selected chat's normal encryption. Optional subscriptions post new articles while DinoX is running, preserve their account and destination, skip existing articles and pause if chat encryption changes. A separate XMPP feed view reads and subscribes to PubSub nodes and publishes text posts and replies under XEP-0472; these posts are not end-to-end encrypted.
- Optional DNSSEC and DANE: Each XMPP account and MQTT broker can independently leave verification off, check supporting domains, or require it. Validated DNS records bind the actual TLS connection before authentication. Proxy connections use an explicitly configured HTTPS resolver through the same proxy; DNS failures do not silently disable verification or select a direct route. Existing account and broker settings remain off.
- Camera filters and adjustments: Adds Cold tone, Sepia, Light leak, Dreamy, Prism light, Fisheye, Vintage TV, Frosted glass, Duo tone and Underwater alongside the existing Grayscale and Warm tone. Brightness, contrast, saturation and sharpness have separate controls, with optional gentle touch-up and low-light enhancement.
- Backgrounds and face accessories: Adds background blur, solid colours, built-in scenes and selection of a still PNG/JPEG image, plus automatic framing. Glasses, hats and beards offer several styles; puppy and karaoke accessories and fireworks, confetti, stars and football animations are also available. Face tracking is limited to one face.
- Join and participant actions: The group-call menu distinguishes starting a new call, joining a live call and rejoining the remembered call room. Adding a participant to an ongoing one-to-one audio or video call prepares a private temporary room and verifies group-call support before moving the existing call.
- Separate device tests: Preferences distinguish call microphone, speaker and camera tests from voice/video-message capture tests. Each test uses its selected configuration, reports its result and releases its recording or preview resources when closed.
- Account server-backup management: Key Management can explicitly delete the selected account's complete server backup while keeping local keys and public-key publications. Pending key-related cleanup is shown separately with a checked reconnect retry.
- Group history period: Personal group settings can retrieve 1–365 days of archived messages, separately for each group and account. With the custom period off, DinoX keeps its automatic rules. “Load now” requests older messages without leaving the room; the server's available history remains the limit.
- History shortcut: One-to-one chats and groups offer “Load messages now” in their chat menu and through Ctrl+Shift+H, documented in the keyboard-shortcut overview. One-to-one requests filter the selected account's archive for that contact; group requests use their saved period.
- Collapsible chat list: The wide-window conversation list can collapse to small contact pictures with orange unread and mention markers. Group rooms show a people badge and private rooms a lock, independently of contact presence. A centred arrow or Ctrl+Shift+L switches views; shrinking the window still uses the automatic narrow-window navigation. The keyboard-shortcut overview now includes message editing, search and dialog controls.
- Feed keyboard shortcut: Open Feeds with Ctrl+Shift+F. Web subscriptions offer a 5-minute to 24-hour interval, defaulting to 30 minutes; automated chat delivery runs only while DinoX and the selected account are online.
Changed
- Offline effect runtimes: Package pins now include matching Google/libwebrtc M152 ABI 40 / IPC 10 libraries, the isolated vision worker, pinned models, licenses and provenance. Ordinary colour filters do not require model inference; effects stay off until selected for the call.
- Call controls and room use: Participant invitations use a compact button, and video effects also apply to MUJI video calls. Calls started in an existing private chat room use that room. Temporary rooms used for one-to-one call conversion have a checked nonpersistent configuration.
- Server administration: Commands are grouped by the selected account's server, target and interface. ejabberd API commands remain distinct from node and standard ad-hoc commands; Prosody commands use their advertised identifiers. The catalog covers ejabberd 26.09, including invitation and password-reset commands when the server exposes them. Forms, action buttons and result text use clearer labels.
- Server-directory search: The contact dialog explains that this searches a server-provided user directory, rather than the local contact list. Known form labels and search instructions are translated without changing the field names or values sent to the server.
- OpenPGP key management: Shows the owning account, assigns explicitly imported private keys without activating them, displays import progress and refreshes the key list directly. Legacy keys can be assigned even when their email identity differs from the account's XMPP address. XEP-0373/0374 keeps its matching
xmpp:identity requirement. - Tray menus: Adds coloured status/action icons on Linux and Windows. The Windows menu includes Show DinoX, follows the application's light/dark theme, scales with monitor DPI and exposes readable names to accessibility tools; high-contrast mode uses native menu items.
- Linux input compatibility: A private compatible IBus client handles the affected input-method versions without replacing the system library or requiring a PPA. Its C17 build settings also avoid the emoji-helper declaration failure with newer compilers.
- Message headers and mention styling: Keeps the sender, date, encryption and delivery indicators together. Mentions use a small indicator beside the header and a subtle side marker in light and dark themes, replacing the full coloured message background. Conversation details adapt their controls and navigation to narrow windows.
- Group hats and member labels: Member lists show readable coloured hat badges instead of plain labels. Hat management separates available labels from assignments, explains that hats do not grant permissions, and shows the selected room and account. Creation, assignment and removal use clearer actions and the choices allowed by the server.
- OMEMO device management: Key dialogs identify the account, contact and device and explain verification, rejection, session reset and device removal. The key list refreshes after changes; a changed fingerprint requires another review instead of applying an action to a replacement key.
- German translations: Completes account-creation headings, sign-in actions and form labels, and adds the new history, hat-management, font and encryption-status text to the German translation and translation templates.
- Linux package-build parallelism: Package jobs can use four compiler jobs and four CPUs, while keeping the existing pinned build dependencies.
- libsoup 3.4 baseline: Source builds and Debian packages now require libsoup 3.4 or newer, so package installation rejects an older incompatible runtime.
Fixed
- Choosing a Linux package: Release downloads, the README and the DEB description now identify the Ubuntu 24.04/Mint 22 binary explicitly. Installation help explains runtime dependencies, APT installation and the AppImage/Flatpak alternatives for Debian Trixie derivatives; development packages are not a workaround for incompatible system libraries.
- Reconnect while avatar or read-state requests are pending: Cancelling a request while changing login protection no longer crashes on an empty asynchronous PubSub result. Avatar reads, uploads and removal retain their cancellation and uncertain-write outcomes; cancelled read-state synchronization and OMEMO bundle publication cannot be mistaken for confirmed success. Applies to the shared Linux and Windows code.
- Repeated login-protection checks: Locally cancelled blocklist, message-carbon and OMEMO device-list requests no longer produce misleading failure warnings during a reconnect. An interrupted device-list request does not report an empty list or fail pending encrypted messages. The replacement connection fetches its state again; real server and transport errors remain visible.
- Feed setup and subscriptions: Separates reading other people's XMPP feeds from publishing a personal feed and explains who hosts posts and how updates arrive. Web-feed intervals are visible before setup and editable for each saved subscription without resetting delivery history or encryption. Missing XMPP feeds show a translated explanation; other server errors remain visible.
- Unicode in feed previews and sharing: Shortened text keeps combining accents, composite emoji and flags intact. Feed decoding recognizes UTF-16/32 byte order with or without a BOM and validates the converted UTF-8. Invalid outgoing text is rejected before queuing or publishing. The implementation is shared by Linux and Windows.
- OMEMO send retries: Pending messages retain their original direct-chat or group-chat type. Missing device lists no longer cause repeated queries for already known recipients. An authoritative empty list stops the send with a translated explanation and an explicit retry, instead of repeatedly attempting encryption. Group sends never treat a room address as a recipient when room state is unavailable.
- Windows TLS with Unicode profile paths: The portable package includes a pinned GIO/GnuTLS module that loads CA certificates from paths containing Cyrillic characters and spaces. Certificate validation remains enabled.
- MUJI readiness confirmation: New outgoing group-call connections wait for the room to reflect the current READY presence, with the Monocles profile's five-second fallback. Incoming connections remain available during the wait, and an existing direct call continues when another participant is invited. Cancellation, stream changes and replaced call owners cannot release stale outgoing attempts.
- MUJI connection ownership: Initial and later participants use the same nickname-based initiator rule as the Monocles MUJI profile proposal, including identical Unicode ordering. Removes the join-order dependency and the mutual-preparation timeout exception while retaining room, device and trust checks. Existing direct-call sessions remain intact when inviting another participant; DinoX continues to use legacy OMEMO for these calls.
- Linux VP8 decoder selection: Checks real key/delta decoding, usable image output and hardware/software latency before selecting VA-API, instead of relying only on a reported decoding profile. Unsuitable hardware uses libvpx; encoder selection remains independent. The short worker-local check does not certify all resolutions or network conditions.
- Accurate call diagnostics: Signaling logs report the actual first SDP payload instead of incorrectly labeling the preferred codec as selected. SDP preference order does not prove which codec is being sent; native codec negotiation remains unchanged.
- Inviting a group-call participant again: Uses a fresh reference for each direct invitation to an existing conference, so a participant who left can be invited again without triggering duplicate-invite protection. Old replies and timeouts are matched to their original invitation; replay checks and room-invitation references remain intact.
- OMEMO sending from fresh profiles: Excludes the current sending device from its own key recipients, so a new profile does not wait indefinitely for a session to itself. Other own devices still receive encrypted copies and missing sessions still block incomplete delivery. Empty recipient payloads fail closed; device identities, trust decisions and published lists are preserved.
- First messages to new encrypted group participants: Prepares pending recipient sessions before sending, even when another group member is already ready. A new participant no longer has to send first to receive subsequent messages. Denied access to a needed key reports a failed send in the current private room instead of silently omitting the participant.
- OMEMO authentication of call fingerprints: Direct and private-group Google/libwebrtc calls wait for the selected device's encryption session before sending a protected DTLS fingerprint. Failed key preparation no longer silently sends an ordinary fingerprint. Once protection is negotiated, later fingerprints must retain the same accepted device identity. Ending a call cancels only its own pending requests; adding a participant preserves the existing direct connection. Rejected incoming setup removes the waiting participant instead of leaving a stalled group call. Peers that do not negotiate the optional extension continue to use ordinary DTLS-SRTP.
- First group-call invitations: An eligible contact's group-call invitation can create its incoming call entry without requiring an existing direct chat. Joining the room and starting media still require accepting the invitation. Incoming invites retain their actual connection and bound recipient, use the existing contact/block policy, and preserve the separate identity checks for live private rooms.
- Long addresses in contact and participant choosers: Directory-search labels can shrink to the dialog width, with their complete text retained for tooltips and accessibility, avoiding GTK sizing warnings while entering long addresses.
- Group-call media and participants: Releases closed peer video attachments, preserves active MUJI presence during room/status updates, shows initial participants and keeps an established conference open when a peer leaves. Video pipelines close asynchronously, and controls recover after the last video peer leaves.
- Call conversion and cancellation: Cancelling the participant chooser restores the invite control. Unsupported contacts and failed room preparation no longer leave conversion controls disabled or partially moved media state. Stale events from a closed call window are ignored.
- Call audio after restart/rejoin: Reapplies selected audio devices and volume when the WebRTC worker is reactivated, instead of retaining an inactive device state.
- Incoming one-to-one calls: Validates JMI initiation and the peer identity before allocating a media session, so invalid initiation cannot leave subsequent transport messages attached to a session that never started.
- Voice-message sending and playback: Keeps a finished recording path until the chat receives it. Playback waits for decoder readiness and completed seeks, preserves positions across cancellation/speed changes, and supports replay after the previous output session has ended.
- Audio-player layout: Bounds the player's width and reduces its play-button size so it does not collide with message actions, including in narrow chat windows.
- Device selection and tests: Prefers exact/stable device identifiers before display-name fallbacks, excludes empty GUID matches and explicitly restores the system-default output. Tests use separate contexts from message playback; interrupted device refreshes restart, and test callbacks are disconnected on completion or cancellation.
- Sticker previews and imports: Identical images update all waiting thumbnail widgets. Folder and XMPP-link imports show a spinner while working, and the animation switch controls sticker playback in the chat. Stopped or superseded previews release their callbacks and files.
- Responsive chat navigation and dialogs: Keeps the selected chat visible when narrowing the window, preserves settings scroll position after device tests, and corrects group-dialog minimum/natural sizing when returning from details.
- Contact and encryption diagnostics: Contact-permission notices can be dismissed. Expected missing OpenPGP publication data is quieter; OMEMO diagnostics distinguish a missing recipient key for this device from local key-store or session failures.
- Edited-message reloads: Resolves correction rows through persisted message identity and preserves the original sender when reloading an edited message.
- Directory requests and administration forms: Discovers the actual search service, handles unavailable or timed-out forms, and cancels obsolete searches. Administration requests and form results retain their account/target context, and malformed or missing display values no longer reach unsafe string formatting.
- Network overview: Includes connected standalone MQTT in the overall status, removes stale provider rows after account changes, and bounds long account labels and the scrolling account list.
- Password changes and account deletion: An offline or failed password change reports an error without overwriting the stored password. Account deletion can offer managed CloudBot cleanup when only cloud management tokens are present.
- Botmother API and backups: Correcting API settings retries a failed server start without requiring an off/on toggle. Profile backups also snapshot an existing bot database when its plugin is disabled and uninitialized, including committed WAL data.
- OpenPGP backup/restore and key switches: Uses the uppercase XEP-0373 backup code, while accepting older DinoX backups; requests the private key's original passphrase before export. Restoring a multi-key backup skips only keys already present. Offline A-to-B-to-A selection no longer retracts the reactivated key, and deactivating XMPP OpenPGP resynchronizes a restored Legacy presence key.
- Windows tray notifications and visibility: Each queued balloon keeps its own action and account/conversation target. Retracting one notification leaves unrelated calls/invites intact; Explorer restart and shutdown release pending actions. Reopening a hidden window through a notification no longer confuses the next tray click, and the status-message action opens a visible dialog.
- Cross-platform bindings and packaging checks: Corrects Windows pointer/format types, preserves required Android JNI exports, and checks the matched video-effect runtimes and Linux SNI sandbox permission without bringing back external libdbusmenu.
- Release and Windows ZIP helpers: Preparing an existing version promotes its changelog and XML entries while preserving the notes and avoiding duplicate releases. Publication rejects development/unreleased metadata until it is promoted to one approved date. The Windows ZIP helper rejects an output directory inside
dist/, keeping the generated archive outside its own source tree. - Avatar context menus: Close the chat-avatar menu when clicking elsewhere, pressing Escape, switching applications, hiding the message or minimizing the chat window. Wait until the initiating mouse button is released before opening, avoiding GTK active-state warnings on repeated clicks. Closed menus release their callbacks and room data while keeping subsequent actions and the fast cached member list intact.
- Windows interface text: Restores a readable 11-point minimum while retaining the Windows font family, larger system fonts and later system-font changes. Applies the intended font hinting and aligns letters to the pixel grid on current GTK versions. Uses the display's text resolution instead of forcing 96 DPI; chat-font preferences remain separate.
- Tor bridge checks: Avoids HTTP/2 session-cleanup warnings when requesting bridges and checking WebTunnel endpoints on Linux and Windows. These short-lived helper requests use HTTP/1.1 while retaining HTTPS certificate validation, timeouts and existing status handling.
- AppImage builds during repository outages: Retries temporary Ubuntu snapshot download failures and rejects incomplete source indexes. Persistent outages now report the failed snapshot fetch clearly, while retaining the exact dependency versions and source checks.
- Windows native type compatibility: Corrects string-array types used by OMEMO trust updates and group hats, along with image and popover bindings in the GTK tests. Layout tests also check whether position measurements succeeded. The changes retain support for the existing Linux GTK baseline.
- OMEMO key publication after receiving messages: Updates the published device bundle only after consumption of a one-time key is safely saved. Concurrent receives, failed publications and reconnects retain pending work and retry delays instead of leaving the published bundle out of sync with the local keys.
- Trusted OMEMO session recovery: Eligible live legacy-OMEMO failures can send a fresh encrypted handshake to the same trusted device in direct chats and eligible private groups whose participants can be identified. A repair deferred by a temporary room or connection change can be sent later without repeatedly replacing the session. This does not recover the contents of an already failed message.
- Encrypted group history and device readiness: Corrects historical private-group sender checks and recipient-readiness updates. Temporary device-bundle failures can be retried, while stale replies and changes in account, room membership or trust cannot complete an obsolete operation.
- Trust changes in existing conversations: Accepting or rejecting a key updates the visibility of messages tied to that exact account and fingerprint. Historical trust indicators use the recorded key identity. Older hidden messages without a recorded fingerprint stay hidden with an explanation; changing trust does not create new-message notifications or bring back cleared history.
- Encrypted group recipients: Private-group messages wait for an actual participant's encryption session instead of being considered sendable with only the user's own devices. If no trusted participant device is available, the chat explains what needs attention.
- Readable encryption errors: Undecryptable messages and their chat-list previews use translated diagnostics. Failed sends explain missing room membership, trusted devices or incompatible encryption settings. Ordinary received text is not mistaken for a local error.
- Missing group history after rejoining: Resets the room's live archive cursor for a new visit and only resumes tracking new messages after catch-up succeeds. A complete response to a limited archive query no longer hides older available messages. Existing archive coverage metadata is rebuilt without deleting local messages or keys.
- Mentions after restart and history loading: Saves mention classification with the message and keeps it scoped to the receiving account and room. Chat markers, unread lists and notifications use the same result across restarts, archived messages, edits and nickname changes, without needing a chat switch to refresh. Full Unicode nicknames and explicit mention references are recognized, while quoted reply text does not create a false mention.
- Pinned chats in the compact sidebar: Pinned conversations retain a visible pin badge when the chat list is collapsed to contact pictures, alongside unread, mute and group indicators.
- Multiline message input and restored controls: Keeps attachment, recording, emoji and send controls aligned when a draft spans several lines. Controls in the initially restored chat refresh as its connection and permissions become available. Switching chats preserves draft formatting, cursor and selection; nickname completion replaces only the word at the cursor. Native text context menus open without stale popover state.
- Reactions, previews and narrow chat content: Reaction buttons stay beside one another and wrap when needed. Website preview images retain their full aspect ratio. Images, files, call rows and previews respect the available chat width instead of forcing the window wider or clipping their controls.
- Member-list refresh and search: An initially empty participant list updates when members arrive. Search handles Unicode names consistently, and reopening a populated list keeps the fast cached path without requiring a new network fetch.
- Chat font settings: A saved font that is no longer installed remains visibly identified and can be reset to System default. Updating the font list or reopening settings no longer silently rewrites the selection. Long font names are shown as plain text; Windows follows its native interface font when available, with Segoe UI as a fallback.
- Provider selection and registration fallback: Offers the provider's registration website when a server refuses in-app registration. Updating the bundled provider snapshot validates a candidate before replacing the last usable list, so an incompatible download cannot erase it.
- Windows Tor build and test setup: Declares the Windows SDK level needed for owned-process cleanup and includes the required crypto library in the noninstalled Tor-startup test's library search path.
- IBus package validation: Recognizes compatible library aliases without falsely rejecting a usable Linux package runtime.
- Tor startup and recovery: Account login waits for the local Tor listener, successful bootstrap and the current proxy port. Restarting or stopping Tor cancels stale starts and callbacks. The Tor switch remains usable during bridge changes so users can stop a failed connection attempt.
- Shutdown of bundled Tor transports: DinoX waits for its own Tor and Lyrebird process tree to stop. Linux process groups and Windows Job Objects preserve unrelated services, including other Tor instances; tray exit timers allow plugin cleanup to finish.
- Flatpak tray fallback: The existing alternative StatusNotifierWatcher has its required targeted permission. Package checks also reject launchers that disable the GTK accessibility backend.
- OpenPGP history after switching encryption: Older XEP-0374 messages from the account's own archive can be read after switching the direct chat to OMEMO. They retain their original encryption label and use the account's stored sender key, with signature, identity and recipient checks; loading history does not switch the current chat mode or start key discovery.
- Tor helpers in local Linux builds: Keeps the pinned Tor, Lyrebird and GeoIP files outside the disposable Meson build directory, so release preparation does not remove WebTunnel support. The preparation command reuses a complete verified runtime; normal application builds do not download helper programs.
- Windows sticker folder imports: Recognizes Windows image file types when importing a sticker folder instead of reporting a folder containing usable images as empty.
- Windows binding corrections: Uses correctly typed backup-fingerprint and webhook-retry lists, native audio-player popover bindings and binary HTTP test responses, avoiding invalid pointer and value conversions during Windows compilation.
- Narrow-window chat transitions: Coordinates initial message rendering with the GTK frame clock and waits for a usable viewport before loading more history. Reaction emoji menus are created on demand; call subtitles avoid repeated layout searches. The compact sidebar no longer forces a blocking rebuild at the start of the chat transition.
- Conversation details: Avoids constructing hidden detail pages while opening a contact or room from either the sidebar or chat menu, reducing the opening delay and stale menu state.
- Encryption controls and device actions: Context-menu shortcuts open the selected conversation's encryption page directly. Composer controls show the current encryption and trust state; trusted and verified remain distinct. Device-key actions have visible buttons, inactive-device removal is clearly marked, and destructive confirmation explains the next action.
- Contact/group dialogs and translations: Equal-sized action buttons, narrower group selection, completed German labels and activity plurals, and Unicode-aware search improve contacts and rooms, including Cyrillic names.
- Delayed ICE acknowledgements: A written transport-info IQ without a timely response no longer tears down an otherwise connected native call. Native ICE determines connectivity; the missing acknowledgement is a debug diagnostic, while actual send failures remain errors.
- Linux packaging: Pins the qualified VP8 decoder runtime across package formats, includes libunbound and its runtime checks, uses the GNOME SDK's Expat when building Flatpak Unbound, and preserves the Vision worker bytes required by its size/hash manifest checks.
- Repeatable interop and Windows checks: Retains bounded native/mixed-client call fixtures, source/identity tracking and cleanup checks. Android-only Monocles fixtures live in the Monocles fork. Windows builds explicitly run DNSSEC/DANE, SASL/TLS, reconnect and account-isolation checks. Login-protection UI checks run in an interactive desktop; test programs and fixture keys are excluded from portable packages. The Windows compiler fixes also cover the DNS-over-HTTPS ALPN binding and completion of asynchronous MQTT reconnects.
Security
- Account login downgrade protection: Validates SCRAM mechanism/binding hashes (XEP-0474) and negotiated TLS versions (XEP-0515). Confirmed SCRAM use is saved per account and prevents later PLAIN fallback. PLAIN-only servers require explicit permission in account settings, including for existing accounts after upgrade; TLS remains mandatory. Invalid proofs and security failures have distinct German and English messages on Linux and Windows.
- Tor reconnect privacy: Disabling an account's SOCKS5 override while global Tor is enabled but not ready retains the override and reports the wait state, instead of reconnecting directly.
- Private profile fields: Fields excluded from public access are not additionally published through unrestricted legacy vCard-temp. Asynchronous profile loads and saves use an account snapshot and reject responses after switching accounts.
- OpenPGP keyring isolation: A missing or unavailable DinoX GnuPG directory produces an error instead of falling back to the operating system's default keyring. Linux and Windows continue to use DinoX's own user-data keyring.
- Scoped key and backup cleanup: Key revocation/deletion is blocked while another account uses that local key. Key-related server-backup cleanup verifies that the backup belongs to the selected key, keeps unrelated/multi-key backups, and preserves a checked retry when cleanup fails rather than claiming success and discarding the local key.
- Botmother disabled state: Removes the incoming-message listener and stops delayed bot starts, Telegram polling and webhook retries when disabled. Re-enabling creates a fresh runtime without duplicate listeners or background work from the previous activation.
- Provider refresh through Tor: Manual provider-directory downloads use the enabled integrated Tor route. They wait or fail when it is unavailable and are cancelled when the route changes, without silently falling back to a direct connection.
- OMEMO key and trust boundaries: One-time key numbers remain reserved after use and across restarts, preventing their reuse for different keys. Recovery and key-management actions recheck the exact account, device identity and trust state; private-group sender checks recheck the room's participant identity information. Stable builds continue to use legacy OMEMO; the OMEMO 2 path remains disabled.
- Asynchronous send targets: File choices, recordings, stickers and location dialogs retain their original account and conversation and recheck current send permissions. Direct transfers in private messages to room participants also retain the original participant identity across retries, preventing a chat switch or nickname reuse from redirecting a send.
- History deletion boundaries: Archive retrieval continues to respect panic wipes, cleared history and message expiry. Excluded archived messages are rejected before decryption, including if the policy changes while an earlier message-processing step is waiting.
- Unavailable Tor stays selected: Tor startup failures, exhausted retries and bootstrap timeouts keep Tor enabled and its XMPP accounts offline. A direct connection requires the user to turn Tor off; an explicit SOCKS5 override remains independent.
- Archived group identities and privacy: Historical group senders are resolved from authenticated archive or encryption evidence instead of whoever currently uses the same nickname. Real-address links are stored only while the room's current disclosure rules allow them.
- OMEMO 2 preparation, still disabled: The inactive OMEMO 2 path also checks the account and encrypted sender/recipient context and discards unauthenticated outer text in key exchanges. Its own-key publication and retry handling have additional safeguards; these changes do not enable OMEMO 2 in stable builds.
Known issues
- Windows sizing diagnostic: An intermittent GTK minimum/natural-height warning remains reported on Windows. Its exact trigger has not been confirmed; the reported case did not restrict normal use.
- Repeated file drops with GTK/X11: Repeated dragging from some GTK3 sources can trigger GTK's
gdk_drop_set_actionsassertion and prevent later drops. This was reproduced without DinoX; the existing root-window controller workaround does not resolve this separate backend failure. Use the attachment button if dragging stops working.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.2_amd64.deb.sha256 sudo apt update sudo apt install ./dinox_2.3.2_amd64.debRun in the download folder. APT installs the required runtime dependencies from your configured Ubuntu/Mint repositories.
This package is not a Debian Trixie binary; use AppImage or Flatpak there. Do not force installation or add Ubuntu repositories to Debian.AppImage
sha256sum -c DinoX-2.3.2-x86_64.AppImage.sha256 chmod +x DinoX-2.3.2-x86_64.AppImage ./DinoX-2.3.2-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.2-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.2-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.2.tar.gz.sha256 tar xf dinox-2.3.2.tar.gz cd dinox-2.3.2 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/.vendor-deps/linux-tor-runtime/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
26 downloads
-
Source code (TAR.GZ)
14 downloads
- Ubuntu 24.04 / Linux Mint 22.x (64-bit Intel/AMD): use the
-
DinoX v2.3.1
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 1m11sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 51m53sBuild / Build AppImage (push) Successful in 1h55m57sBuild / Build Flatpak (push) Successful in 47m38sreleased this
2026-10-05 03:15:45 +02:00 | 348 commits to master since this releaseDinoX v2.3.1
Modern XMPP client with extended features.
What's New
Highlights
- Updated desktop call engine: Google/libwebrtc M152 brings refreshed Linux and Windows runtimes, hardware-assisted video where available, independent software fallbacks, and fixes to direct-call and private-room MUJI negotiation.
- Safer profile maintenance: Backups, restores, password changes, history resets, and profile deletion now coordinate database snapshots, exclusive profile ownership, and recoverable maintenance transactions.
- Clearer contact permissions: Contact dialogs and conversation details show the actual presence subscription state, offer explicit request and grant actions, and report failures without inventing mutual permissions.
Added
- Desktop hardware video codecs: H.264 can use VA-API/NVENC encoding and VA-API/NVDEC decoding on supported Linux systems, and Media Foundation on supported Windows systems. Encoding and decoding choose hardware independently and fall back to software when initialization or processing fails. Linux VP8 reception can use VA-API when the driver exposes the required decoding profile; VP8 encoding remains on the CPU. VP8 stays the initial preference, with VP9 and H.264 selected from shared peer capabilities.
- Visible OMEMO key-access failures: Direct messages waiting for a contact's encryption keys now report denied server access. Subscription requests, grants, and contact actions stay bound to the selected account, with live permission state and retryable failures. The affected controls and error messages include updated German translations.
Changed
- Private-room group calls: MUJI preparation follows reflected room presence, correlates preparation generations, and freezes conference content names, payload IDs, packetization times, codec dependencies, and feedback before READY presence and native media commitment. Explicit BUNDLE mapping is negotiated with peers that support it. New locally created conference capabilities omit optional RRTR; existing READY maps and adopted calls retain their negotiated parameters.
- Direct-call negotiation: Jingle answers and ICE candidates retain the original offer's content order and identities. Description-level and payload-level RTCP feedback, wildcard feedback, and reporting intervals survive SDP conversion, while an answer can omit optional feedback. Direct 1:1 RRTR remains optional.
- Consistent encrypted backups: Backup snapshots wait for admitted message processing to finish and include the related plugin databases. Archive progress follows the messages actually admitted to that snapshot, reducing mismatches between stored messages and restored history state.
- Recoverable offline profile operations: Restore, password changes, history reset, and profile deletion are applied before normal databases and plugins start, under an exclusive profile lock. Interrupted operations retain owned staging and rollback state; maintenance preserves the attachment encryption key and is serialized with account removal and shutdown.
- Release packaging: Linux and Windows packages use pinned M152 runtimes and optimized release defaults. Runtime checks cover codec dependencies, worker lookup, provenance, and package contents. Debian packaging avoids a second application compilation, Flatpak source copies exclude local build outputs, and AppImage verification has a budget for the complete package checks.
- Regression coverage: Expanded tests cover multi-account OMEMO state, profile locking and crash recovery, SQLCipher backup and password changes, MUJI preparation and native mappings, scoped RTCP feedback, contact permissions, Unicode rendering and backups, and Windows fixture cleanup and binding types.
Fixed
- Failed profile password checks on Windows: Offline maintenance closes the database handle when opening or validating an encrypted database fails, allowing Windows to release the file for cleanup and retry.
- Legacy OMEMO startup and recovery: New device registration checks the account's published device list and bundle identity before publication. Bundle discovery no longer creates encryption sessions prematurely; sessions are prepared when sending messages or encrypted Jingle transfers. A bounded trusted-device key transport can recover a missing prekey, while archived receive state and session persistence remain transactional.
- Incoming and queued OMEMO messages: Direct chats can display authenticated decrypted messages even when the outgoing mode is plaintext. Device-list changes revalidate queued sends through normal encryption, and failed direct-message key queries produce a retryable local error. Account isolation, trust choices, and the selected encryption mode are preserved; OMEMO 2 remains disabled in production.
- Groupchat archive collisions and replies: Messages with conflicting personal-archive IDs no longer suppress distinct room messages. Groupchat references and replies use the room-authorized stanza identity, and ambiguous targets are rejected.
- Call setup and teardown: Early remote ICE candidates are buffered until the session can accept them. Closed native sessions are destroyed outside callback locks, failed MUJI peer sessions are retired, and removed participant widgets are cleared. Native MUJI answers reject RTX payloads whose primary codec is absent.
- Unicode text and optional previews: Link parsing, formatting, quotes, and highlighting operate on the original UTF-8 text instead of offsets from a lowercased copy. Optional data-URI thumbnails preserve their metadata, and unsupported previews retain normal file and download controls.
- Windows backup paths and runtime caches: A bundled native archive helper handles backup and restore filenames containing spaces or non-ASCII characters. Certificate bundles and GStreamer registries use the runtime cache directory, keeping startup cache work away from the profile before its lock and restore checks.
- Tor bridge startup: Bundled Lyrebird and obfs4 transports launch correctly from directories containing spaces or Unicode characters. Tor receives a supported executable argument and the corresponding working directory on Linux and Windows.
- GTK focus and XMPP stream ownership: Text-widget focus is cleared at the appropriate lifecycle boundary, and stream modules track attachment ownership so a reused module cannot leave handlers bound to the wrong stream.
- XMPP error handling: Diagnostic text no longer masks the actual stanza error condition, regardless of XML child order. Native OMEMO failures retain their underlying Signal error details for diagnosis.
Security
- Packaged Tor update: Update Tor from 0.4.9.8 to 0.4.9.12. Linux and Flatpak source pins, Windows package verification, and runtime inventories use the verified artifacts; the Windows package and its upstream signature are mirrored in Forgejo
vendor-deps. - Encrypted profile protection: An existing OMEMO database with a missing key fails explicitly rather than receiving a replacement key. Account-related message state stays on its actual pipeline object, and payload-less legacy key transports cannot expose an unauthenticated outer message body.
- Data-preserving cache cleanup: Cache clearing keeps durable account data and active media intact. Profile deletion retains its pending request across shutdown, and restore and maintenance reject unsafe ownership and filesystem paths.
- Automatic API certificates: Certificate renewal and removal recheck the current API mode and custom certificate settings when activated, preventing stale controls from changing manually configured certificates.
- Private-room call invitations: Direct MUJI invitations for an already joined room require a current participant with the matching disclosed full JID and an active private-room lifecycle. Reconnects and occupant changes invalidate stale acceptance work.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.1_amd64.deb.sha256 sudo apt install ./dinox_2.3.1_amd64.debAppImage
sha256sum -c DinoX-2.3.1-x86_64.AppImage.sha256 chmod +x DinoX-2.3.1-x86_64.AppImage ./DinoX-2.3.1-x86_64.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.1-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.1-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e sha256sum -c dinox-2.3.1.tar.gz.sha256 tar xf dinox-2.3.1.tar.gz cd dinox-2.3.1 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m152-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --buildtype=debugoptimized --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version # For Tor/obfs4/WebTunnel, first follow the optional private Tor runtime section in BUILD.md. DINOX_TOR_DATA_DIR="$PWD/build/release-deps/share/tor" ./build/main/dinox )Downloads
-
Source code (ZIP)
23 downloads
-
Source code (TAR.GZ)
9 downloads
-
DinoX v2.3.0
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 55sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 48m8sBuild / Build AppImage (push) Successful in 1h11m12sBuild / Build Flatpak (push) Successful in 41m13sreleased this
2026-08-26 20:43:41 +02:00 | 397 commits to master since this releaseDinoX v2.3.0
Modern XMPP client with extended features.
What's New
Highlights
- Reliable calls across devices and reconnects: One-to-one Google/libwebrtc calls now implement the current XEP-0353 signalling lifecycle, including ringing, final call state, simultaneous-call tie-breaking, active-device migration and passive reconstruction from Carbons and MAM. Archived signalling never starts media or rings again, and private-room MUJI calls remain on their separate lifecycle.
- Room avatars before joining: Bookmarked rooms can obtain and verify their XEP-0486 avatar before the first join without delaying room lists or starting unbounded network work.
Added
- Room avatars before joining: Bookmarked rooms can obtain their XEP-0486 avatar from
muc#roominfo_avatarhashand the room vCard before the first join. Image bytes are accepted only when their SHA-1 hash was advertised by the room. Status code 104 refreshes changed or removed avatars after joining. - Complete XEP-0353 0.8.0 signalling: One-to-one Google/libwebrtc calls support
ringingandfinishalongside the existing proposal actions, including final reasons, migration metadata and the required message-storage hints. Malformed or conflicting events are rejected while known legacy wire variants remain accepted for interoperability.
Changed
- Bounded room-avatar discovery: Pre-join discovery runs one room at a time after a short low-priority delay, deduplicates account/room work, caps server-provided representations, and fences disconnects and superseded results. Bounded batches refill from the authoritative bookmark set instead of dropping rooms above the active queue limit, and reconnects discard freshness state from the previous stream. Image decoding, hashing and encrypted cache I/O stay off the UI thread; conference and member lists continue to read only from the local avatar cache.
- Room-avatar interoperability: Live ejabberd and Gajim tests cover discovery before joining, joined-room refreshes, publication and removal. The smoke test showed no visible UI stalls; it was not a large-room timing benchmark.
- Persistent multi-device call state: Call ownership is scoped by account, peer and session ID, survives restarts, and expires bounded recovered proposals. MAM and Carbon replay is ordered, deduplicated and passive; another own device accepting or ending a call settles the local state without allocating a media worker. The production call engine remains Google/libwebrtc, with RTP disabled.
Fixed
- Attachment actions after transfer completion: File, image and video rows retain their exact backing message across restart and archive replay. Reply, reaction and delete actions update as soon as the message identifiers become available instead of remaining unavailable or targeting transport metadata.
- Visible attachment controls on Windows: Disabled symbolic message-action icons remain visible in compact attachment toolbars, while their unavailable state is still clearly dimmed.
- Inline MP4 playback startup: Preview generation and playback use separate generation ownership, bounded startup timeouts and deterministic temporary-file cleanup. Starting playback while a thumbnail is still being prepared no longer leaves a stale pipeline, and Windows packages now verify the complete MP4/H.264/AAC playback runtime.
- Contact conversation selection: Opening the contact chooser no longer treats the first visible contact as an implicit selection. The start button becomes available only after an explicit selection, avoiding a disabled button for a row that merely appeared selected.
- Legacy GTK file drops on X11: DinoX removes only GTK's conflicting private root-window drop controller on affected native X11 versions. The application COPY target, portal drops, Wayland and Windows behavior remain unchanged.
Known issues
- Repeated file drops on X11: The open GTK issue #3755 can log a
gdk_drop_set_actionscritical from the second file drop onwards. File sending continues normally and DinoX release launchers do not make GLib criticals fatal. Wayland and Windows are not affected by this X11-specific GTK bug; developer runs that explicitly enable fatal criticals can terminate on the assertion.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.3.0_*.deb.sha256 sudo apt install ./dinox_2.3.0_*.debAppImage
sha256sum -c DinoX-2.3.0-*.AppImage.sha256 chmod +x DinoX-*.AppImage ./DinoX-*.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.3.0-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.3.0-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e tar xf dinox-2.3.0.tar.gz cd dinox-2.3.0 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m150-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version DINOX_TOR_ALLOW_SYSTEM_FALLBACK=1 ./build/main/dinox )Downloads
-
DinoX v2.2.9
StableAll checks were successfulBuild / Validate Manual Selection (push) Has been skippedBuild / Release Preflight (push) Successful in 55sBuild / Mirror AppImage Runtimes (push) Has been skippedBuild / Core Build (push) Successful in 44m48sBuild / Build AppImage (push) Successful in 1h5m10sBuild / Build Flatpak (push) Successful in 37m13sreleased this
2026-08-25 05:14:44 +02:00 | 412 commits to master since this releaseDinoX v2.2.9
Modern XMPP client with extended features.
What's New
Added
- Read-state synchronisation between devices: An optional XEP-0490 setting synchronises the latest displayed position through the account server for one-to-one chats, group chats, and private MUC messages. This remains separate from contact-visible read receipts, uses server assistance only when advertised, and otherwise falls back to regular private PEP storage.
- Private-room read receipts: Read receipts can now be configured per private room. Sent messages show how many verified room participants have read them without folding different readers into one room-wide state.
Changed
- Stable displayed-marker references: XEP-0333 markers use sender stanza IDs for one-to-one chats and MUC private messages, and room-assigned XEP-0359 IDs for group-chat messages. Read pointers move forward only. Early one-to-one and MUC-private markers are applied after the matching live or archived message appears, while unknown group-chat targets are rejected.
- Bounded avatar loading: Avatar cache reads run outside the GTK main thread, duplicate requests share one load, and memory use is bounded. Large rooms fetch participant avatars on demand with bounded prefetching instead of starting an unbounded burst.
Fixed
- Account avatar publication: The independent XEP-0084 and vCard/XEP-0153 publication paths are coordinated across initial connection and reconnect, including directed room presence. Transient vCard fetch failures no longer overwrite the stored avatar, and interrupted or superseded publication attempts cannot restore stale state.
- Avatar state isolation: Avatar assignments, source priorities, waiters, observers, and room occupants remain scoped to the exact account and JID, while validated image bytes are deduplicated by content hash. Live room updates cannot be replaced by an older membership snapshot. Explicit removals clear the mapped avatar, while invalid metadata is ignored without changing verified state.
- Delivery and read indicators: Receipts continue to match when a server rewrites an outer stanza ID, when a receipt arrives before its message, or when a MUC echo supplies the authoritative room ID.
- Private-room encryption startup: Incoming encrypted messages now wait for an already-running room-information query before applying the conversation encryption policy, instead of being discarded while a newly opened private room still temporarily reports no encryption.
- Read-receipt privacy and lifecycle: Delivery and displayed responses are limited to eligible, unblocked contacts or current room occupants. Malformed, ambiguous, cross-account, and wrong-room references are rejected; reconnects fence stale operations, and remote read-state updates no longer clear unrelated notifications.
- Persistent read pointers: Message and content-item read positions are stored together and reconciled when an attachment item arrives after its message, avoiding read-state regressions after restart or history catch-up.
Installation
Ubuntu 24.04 / Linux Mint 22 (.deb)
sha256sum -c dinox_2.2.9_*.deb.sha256 sudo apt install ./dinox_2.2.9_*.debAppImage
sha256sum -c DinoX-2.2.9-*.AppImage.sha256 chmod +x DinoX-*.AppImage ./DinoX-*.AppImageThe matching
.AppImage.sources.tar.xzfile is a separate compliance download.
It is not required to install or run DinoX.Flatpak
sha256sum -c dinox-2.2.9-x86_64.flatpak.sha256 # Required runtimes are resolved automatically from the bundle metadata. flatpak install --user ./dinox-2.2.9-x86_64.flatpak flatpak run im.dinox.dinoxBuild from Source
( set -e tar xf dinox-2.2.9.tar.gz cd dinox-2.2.9 # Install the normal distribution development packages from docs/internal/BUILD.md. test "$(uname -m)" = x86_64 bash scripts/prepare-linux-source-build-deps.sh export DINOX_LIBWEBRTC_RUNTIME_ROOT=$PWD/.vendor-deps/libwebrtc-m150-linux-x86_64-runtime export DINOX_LOCAL_LIBOMEMO_C_ROOT=$PWD/.vendor-deps/linux-source-deps export PKG_CONFIG_PATH=$DINOX_LOCAL_LIBOMEMO_C_ROOT/lib/pkgconfig${PKG_CONFIG_PATH:+:$PKG_CONFIG_PATH} ./scripts/check-libwebrtc-linux-runtime.sh "$DINOX_LIBWEBRTC_RUNTIME_ROOT" meson setup --wipe --prefix=/usr build -Dlocal-libomemo-c-root="$DINOX_LOCAL_LIBOMEMO_C_ROOT" -Dplugin-mqtt=enabled -Dplugin-rtp=disabled -Dplugin-google-webrtc=enabled -Dgoogle-libwebrtc-wrapper=enabled -Dgoogle-libwebrtc-runtime-root="$DINOX_LIBWEBRTC_RUNTIME_ROOT" -Dgoogle-libwebrtc-test-oracle=false -Dgoogle-libwebrtc-tests=false -Dlocation-sharing=enabled -Dplugin-http-files=enabled -Dplugin-ice=enabled -Dplugin-omemo=enabled -Dplugin-openpgp=enabled -Dplugin-notification-sound=enabled ./scripts/build.sh ./build/main/dinox --version DINOX_TOR_ALLOW_SYSTEM_FALLBACK=1 ./build/main/dinox )Downloads
-
Source code (ZIP)
34 downloads
-
Source code (TAR.GZ)
10 downloads