Repository navigation
OmaQ v0.8.0
Pre-releaseOmaQ v0.8.0 is the first public pre-release of invite-only chat for the Omarchy bar. It has no accounts, phone-number discovery, project-operated chat server, or telemetry.
Highlights
- Signal Double Ratchet protection for DirectChat, with no plaintext fallback
- Stable public-key binding for direct windows, history, unread state, files, receipts, and preferences
- Private GroupChat with roles, presence, moderation, typing, reactions, member-aware receipts, files, and images
- Direct voice calls with explicit Answer, Decline, and Hang up controls
- Explicit file acceptance, private image staging, canonical image validation, and an 8 MiB attachment limit
- Unicode emoji-only messages rendered at a fixed 56-pixel size
- Local identity protection, export validation, confirmed import, recovery guards, and fail-closed warnings
- Per-conversation Auto-open, global notification mute, themes, sounds, message scaling, and unread controls
- A 36-image illustrated user guide
Privacy model
OmaQ stores identity, contacts, Ratchet state, preferences, and history on your machine. It uses public Tox bootstrap and Transmission Control Protocol relay nodes operated by community volunteers. Relay operators cannot read message contents, but they can observe ordinary connection metadata.
OmaQ disables direct User Datagram Protocol discovery and hole punching, so contacts do not receive each other's IP addresses.
Install
Follow the source installation instructions. The repository does not include a generated helper binary. Build the Protocol-13 helper locally after installation and after every source update.
Known limitations
- Arch User Repository packaging remains paused
- Private groups survive Quickshell and Omarchy Shell reloads only while the detached helper keeps running
- A computer restart, helper crash, or helper cold start cannot reconstruct a private Tox New Group Chat from its Chat ID; another member may need to invite the identity again
- Native separate-network, three-peer fault-injection, multi-monitor, and floating-versus-tiling acceptance remain incomplete
- The historical Protocol-10 to Protocol-7 encrypted-message test remains inconclusive because its relay endpoints did not remain connected