byGalax
f9bbcdee47
The real cost in the "frame by frame" stutter wasn't the custom capture path — it was LiveKit re-encoding via VP9 software with L3T3_KEY SVC (three spatial × three temporal layers, all CPU). Switching the per-publish codec to H.264 lets Chromium's hardware encoder take over on Windows and sidesteps the SVC mode entirely (H.264 has no SVC). Also pushes `contentHint = 'detail'` on the track — setScreenShareEnabled does this internally, the manual publishTrack paths had been missing it, which changes how the encoder allocates its frame budget for static UI content. Auto preset default framerate 60 → 30. 60fps desktop share burns three full-res encodes per frame at sizes up to 4K; 30 is what getDisplayMedia practically delivers anyway. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@chat-app/desktop
Tauri v2 + React + Vite + Tailwind desktop client (macOS / Windows / Linux).
Prerequisites
- Node 22+, pnpm 9+
- Rust + Cargo (install via https://rustup.rs)
- Platform build deps:
- macOS: Xcode Command Line Tools
- Linux:
libwebkit2gtk-4.1-dev,build-essential,libssl-dev(Debian/Ubuntu) - Windows: Microsoft C++ Build Tools + WebView2
Dev
# from repo root
pnpm install
pnpm desktop:dev # tauri dev — launches Vite + native window
pnpm desktop:build # production bundle per platform
Layout
src/— React app (Vite bundles intodist/).src-tauri/— Rust backend.main.rswires Tauri plugins.vite.config.ts— port1420, HMR on1421, aliases to shared packages.
Secure Storage
Session tokens + user private keys live in Stronghold (tauri-plugin-stronghold).
Local message history lives in SQLite (tauri-plugin-sql), DB file encrypted at rest.