Alpha fermée

Chatter: a shared Rust client for private conversations

Une messagerie du quotidien : échanges privés chiffrés, appels vocaux et protection optionnelle des métadonnées par Shield, routage onion Tor et boîtes anonymes. Rust et Slint partagent le cœur et l’interface entre les builds. Go, Protobuf/Connect RPC, HTTP/3/QUIC, PostgreSQL, Redis et Temporal assurent le service. Android et Linux sont les priorités actuelles.

La présentation détaillée du projet est actuellement disponible en anglais.

A closer look at Chatter

These captures come from my own Android phones. The conversations and channels are fictional demo content. Chatter is in closed alpha.

More room on a tablet

The landscape layout keeps the conversation list beside your messages. Captured on a Samsung Tab S9 Ultra development build, with a fictional private mesh conversation.

Chatter tablet development build in dark mode, showing a fictional private mesh conversation

Mesh chat, without the Chatter server

Nearby devices can exchange messages over Bluetooth Low Energy. I disabled Wi-Fi and mobile data on my phone and tablet, then sent the message shown in this recording. This is a real nearby-device exchange, not a multi-hop range test.

Public #mesh channels are readable by nearby participants. Private mesh messages use Noise encryption; nicknames are self-asserted until you verify the peer. Optional Nostr relays require internet. Mesh and Tor-based Shield are separate features.

More than text

A captioned photo, GIF and two-photo album. Real app recording with AI-generated demo attachments.

A message arrives

Typing indicator, incoming message and conversation movement. Silent screen recording.

A call without losing your place

Switching between full-screen and compact views during a connected voice call. Silent screen recording.

Les problèmes difficiles que je résous

  • Sharing the Rust application core and Slint UI while handling native permissions, notifications, media devices and app lifecycle on each platform. Android and Linux are the focus; Windows build support and macOS packaging exist, and the iOS UI port is in progress.
  • Private conversations require end-to-end encryption through libsignal. The client refuses plaintext fallback when encryption is required. Public channels are a separate mode and can carry service-readable content.
  • Shield routes RPC traffic and attachment transfers through Tor when enabled and connected. Blind-signed anonymous mailbox tokens reduce account-to-mailbox linkage. This protects metadata without promising zero metadata or immunity to traffic analysis.
  • Multi-device identity, key changes, background delivery and reconnect behavior need to remain consistent across the shared core and native platform adapters.
  • LiveKit/WebRTC calling with a verification emoji display and compact or full-screen call views. The screenshots show a connected voice call between two Android test phones.
  • Encrypted local history through SQLCipher, encrypted attachment handling, and an operational privacy model that also considers logs, retained metadata and key custody.

La pile technique

ClientRust + Slint, shared application logic and UI, native platform adapters
BackendGo, Protobuf/Connect RPC, HTTP/3/QUIC with HTTP/2 fallback, Temporal workflows and SpiceDB authorization
DataPostgreSQL, Redis, object storage and client-side SQLCipher
Privacylibsignal, optional Shield mode, Tor onion routing and blind-signed anonymous mailboxes
CallsLiveKit + WebRTC; platform-specific media and audio integration
InfrastructureOVHcloud in France, containers, systemd and infrastructure as code

Analyses approfondies sur le blog

Demander un accès à l’alpha →

Pourquoi c’est ici

Beaucoup de gens savent parler d’architecture. Ici, c’est moi qui la construis réellement sur toute la pile — cryptographie, backend, clients natifs et l’infrastructure qui le fait tourner. C’est de là que vient le travail d’idée à production, de blocs de construction, de revue d’architecture et d’audit d’applications IA — appliqué d’abord à mon propre code.

Status: closed alpha. Platform readiness and privacy features are still developing. An independent security audit is not being claimed.

Vous voulez ce type de travail sur votre produit ?

Un appel gratuit de 30 minutes. Dites-moi où vous en êtes ; je vous indiquerai le chemin le plus rapide vers la mise en production.

Réserver un appel de découverte gratuit