Deskdrop focuses on absolute local privacy, timeline-first clipboard control, and deep hardware continuity. Explore the technical details that power our local mesh network.
Traditional cross-device clipboards silently hijack your local OS pasteboard, exposing your clipboard history to race conditions and accidental overwrites. Deskdrop completely redesigns this flow by isolating incoming copies in a sandboxed, visual Activity Feed.
By bypassing sluggish web wrappers, Deskdrop communicates directly with operating system low-level APIs via a unified Rust core. This guarantees responsive background tasks and seamless state synchronization.
Deep integration with Apple Silicon system Nap controls and native menu bar UI elements for sub-second synchronization.
// macOS Native App Nap and Status Menu Core
import Foundation
import AppKit
func preventAppNap() -> NSObjectProtocol {
let reason = "Active Peer-to-Peer file pipeline stream"
return ProcessInfo.processInfo.beginActivity(
options: [.idleSystemSleepDisabled, .suddenTerminationDisabled],
reason: reason
)
}
func syncClipboardWithCore() {
let pboard = NSPasteboard.general
if let contents = pboard.string(forType: .string) {
// High-speed JNI/FFI Fused Core Call
deskdrop_bridge_send_clipboard(contents)
}
}Deskdrop implements a chunk-based transfer architecture designed to survive network disruption. Files are parsed into 256KB block sizes and streamed peer-to-peer over encrypted sockets.
We are actively developing security enhancements to make local discovery entirely anonymous before trust authentication takes place.
Moving from friendly-name discovery in plaintext local broadcasts to cryptographically generated UUIDs to protect network fingerprint privacy.
Correcting Windows socket IPC bindings to support active diagnostic state relays and precise file progress telemetry identical to our macOS client.
Wiring real-time bandwidth and signal metrics into active socket paths to dynamically adjust file transfer chunk sizes under shifting Wi-Fi conditions.
Upgrading device authorization workflows to require explicit cryptographic key exchanges and signature verification before establishing network state synchronizations.
Our features map directly to our 4-phase core reliability roadmap. Check out exactly what is being tested right now in our live tracker.
Explore the Roadmap