How yokeshwarb/qurb works
qurb is private, device-to-device cloud storage: users set up a device, pair another, and sync files directly with end-to-end encryption. Desktop and Android interfaces expose file management and sharing, while the shared Rust engine handles synchronization, storage, keys, and peer communication. Rendezvous helps devices discover and connect; a separate relay implementation forwards opaque traffic, though the README says server deployment is not yet built. Some internal wiring is not shown in the excerpts, so uncertain relationships are omitted or marked unverified.
Main entry points: lib.rs Sync engine · daemon.rs CLI and daemon · connect.rs Peer connection · main.rs Desktop window
Components 19
User clients
- Desktop window
crates/desktop/src/main.rs - Desktop commands
crates/desktop/src/commands.rs - CLI and daemon
crates/qurb/src/daemon.rs - Android app
android/app/src/main/java/com/qurb/MainActivity.kt - Android engine bridge
android/app/src/main/java/com/qurb/Qurb.kt - Android sync worker
android/app/src/main/java/com/qurb/SyncWorker.kt - Mobile FFI
crates/mobile-ffi/src/lib.rs
Sync and storage
- Sync engine
crates/engine/src/lib.rs - Version reconciliation
crates/sync/src/reconcile.rs - File store
crates/storage/src/store.rs - Filesystem watcher
crates/watcher/src/watcher.rs - Key management
crates/keys/src/vault.rs
Device networking
- Peer client
crates/peer/src/client.rs - Peer connection
crates/peer/src/connect.rs - Peer server
crates/peer/src/server.rs
Connection services
- Rendezvous client
crates/signal/src/client.rs - Rendezvous service
crates/signal/src/server.rs - Opaque relay
crates/relay/src/server.rs
Other components
- Device owner
Connections 22
- Device owner → Desktop window: uses
README.md - Device owner → Android app: uses
README.md - Desktop window → Desktop commands: invokes
crates/desktop/src/main.rs - Desktop window → CLI and daemon: hosts daemon
crates/desktop/src/main.rs - Device owner → CLI and daemon: runs setup and sync
README.md - Android app → Android engine bridge: calls
android/app/src/main/java/com/qurb/MainActivity.kt - Android engine bridge → Mobile FFI: uses bindings
android/app/src/main/java/com/qurb/Qurb.kt - Android sync worker → Mobile FFI: runs sync
- CLI and daemon → Sync engine: runs sync engine
- Sync engine → File store: stores file data
- Sync engine → Version reconciliation: resolves versions
- Sync engine → Peer client: syncs with peers
- Sync engine → Peer server: serves peers
- Sync engine → Key management: uses device keys
- CLI and daemon → Filesystem watcher: tracks file changes
- Peer client → Peer connection: establishes connection
crates/peer/src/client.rs - Peer client → File store: fetches content
crates/peer/src/client.rs - Peer server → File store: answers requests
crates/peer/src/server.rs - Peer connection → Rendezvous client: discovers peers
- Rendezvous client → Rendezvous service: exchanges rendezvous messages
crates/signal/src/client.rs - Rendezvous service → Peer connection: introduces devices
- Peer connection → Opaque relay: falls back to relay