Link All

A local-first, zero-cloud continuity engine for resumable file transfers, clipboard synchronization, and hardware interaction across mixed operating systems.

Link All bridges macOS, Windows, Android and Linux without relying on cloud infrastructure or external routing servers. All communication takes place point-to-point over local wireless networks (Wi-Fi, LAN, or standalone Wi-Fi Direct / Mobile Hotspot connections).

At its core is an event-driven asynchronous Rust daemon (linkall-core), designed for zero idle resource consumption and low-latency local IPC with platform-native graphical frontends.

Core capabilities

Resumable file transport

- Zero-copy memory pipelines, adaptive chunk batching and geometric socket auto-tuning - Resumable transfers: mid-transfer interruptions resume without starting over - Fast entropy sampling: incompressible binaries (.mp4, .zip, .jpg) bypass CPU compression cycles

Real-time universal clipboard and timeline

- Cross-platform activity feed: text, URLs or image payloads copied on one device appear in a searchable local history ring buffer with pinning and tagging - Configurable content filtering: clipboard contents are evaluated against local heuristic rules and regular expressions before broadcasts, to keep passwords, OTPs, API keys and credit cards from persisting on unattended hardware - Deduplicated string caching across C-FFI boundaries for high-frequency IPC updates

Extended modules

- Remote file browsing: search, preview and fetch files on a paired device. A phone can browse a computer's folders once "Let devices browse files" is enabled (off by default). A computer can browse a phone with the Android build from GitHub Releases; the Google Play build leaves this out, because Play limits all-files access to file managers - Notification and call handoff: mirror SMS messages, phone call alerts and application notifications to desktop notification centers - Power and battery monitoring: surface remote battery status (0–100%) and charging states in desktop system trays - OS-level sleep immunity: platform power management primitives keep bulk transfers from being suspended

Cryptography and session security

Device discovery over mDNS does not imply trust.

- End-to-end encryption: ephemeral Curve25519 (X25519) ECDH key exchanges, HKDF-SHA256 key derivation, ChaCha20-Poly1305 authenticated encryption - Replay protection: strictly increasing 64-bit counter nonces - Memory zeroization of secret Diffie-Hellman keys and session material - mDNS privacy: friendly device names are obfuscated during general broadcasting; only unprivileged UUID identifiers are visible until pairing is verified - Code-verified pairing: the same security code is shown on both devices; a request stays open for 60 seconds and always ends the same way on each side. Pairing can also be done by scanning a QR code, valid for 10 minutes - Reinstall-aware trust: reinstall gives a device a new identity, and pairing the new install replaces its old entries

Configuration and local storage

- settings.json: user runtime configurations, interface bindings and custom filtering heuristics - peers.json: locally cached network peers, mDNS mappings and device nicknames - trust.json: persistent public keys of verified trusted nodes - history.json: bounded NDJSON ring buffer of historical payloads and activity events - identity.key: the device's private identity key (32 bytes). Its hash is the device ID, so deleting it makes the device look new to every paired device

Caution: the identity.key file contains the device's private identity keys used for network authentication and DH key exchange. It should not be exposed, committed, or transferred across insecure channels.

License

GNU Affero General Public License v3.0