Notes That Never Lose Their Place
A Data Model Built For Change
{{SECTION_SUBTITLE}}
Stable Identifiers and Tombstones
Field-Level Versioning and Intents
The Sync Pipeline That Earns Trust
Delta Feeds and Checkpoints
Background Scheduling That Respects Power
Backoff, Retries, and Rate Limits
Offline-First, Human-First Experience
Security, Privacy, and Trustworthiness
End-to-End Encryption With Selective Sharing
Encrypt note bodies and attachments with keys only devices hold, while enabling linkable structure needed for sync. For collaboration, derive per-note or per-space keys, rotate them safely, and share through authenticated channels. Keep servers blind to content yet able to route changes efficiently.
Key Management Across Devices
Provide intuitive, secure enrollment flows using QR codes, passkeys, or hardware-backed escrow. Clearly label which devices are authorized, expose revocation, and require reauthentication for sensitive actions. When a phone is lost, recovery should preserve privacy first while restoring access without mysterious, irreversible gaps in history.
Testing, Telemetry, and Real-World Confidence
Deterministic Simulations of Bad Networks
Telemetry, Health Indicators, and Alerts
User-Facing Diagnostics That Respect Privacy
Performance, Scale, and Sustainable Costs
Compaction, Garbage Collection, and Snapshots
Retain detail for recent edits while compressing or summarizing the distant past. Periodically seal snapshots so recovering clients jump ahead safely. Garbage collect unreferenced blobs and expired tombstones responsibly, always keeping cryptographic proofs or hashes that guarantee history remains auditable when necessary.
Payload Budgets and Compression Choices
Cap request sizes, stream large bodies, and choose codecs carefully based on data shapes. Textual deltas favor Brotli; mixed attachments might need zstd or none. Measure on real devices; celebrate fewer round trips more than theoretical throughput that drains batteries and frustrates travelers.
Sharding, Multiregion, and Time Travel
Partition data by account or workspace, then place replicas near readers. Use logical clocks and append-only histories to enable rollbacks when necessary. A carefully planned layout keeps latency low, isolates noisy neighbors, and permits graceful restores after rare but inevitable operational surprises.
All Rights Reserved.