Scheduled
8 min read By NT²
Replica batch under the hood — packet shapes
Tech
Blind sync is easier to trust when you can picture the packet. The edge sees shapes, sizes, and progress—not titles, notes, or a searchable attic of your secrets.
Tagged: sync
7 posts
Scheduled
8 min read By NT²
Offline-capable is not sync later if lucky
Tech
Many apps call themselves offline-capable when they mean a read-only cache and a queue that hopes the tower returns. A local-first vault puts full CRUD on the device first. Sync is an optional second path.
Scheduled
8 min read By NT²
What the Workers are allowed to see
Tech
Zero-knowledge is not a slogan about HTTPS. It is a permission list for the edge: what Workers may store, route, and bill for—and what they are never allowed to learn.
Scheduled
8 min read By NT²
Vault profile is section KV, not one mega-row
Tech
Salt, Key DID public material, sync cursors, and onboarding prefs are not one fat SQL row. They live as named vault profile sections—so backup, sync, and unlock can each touch only what they need.
Scheduled
1 min read By NT²
Offline by default is not offline-only
Stories
A vault can work offline and still offer sync. The difference is whether the cloud becomes the owner of the data or just a blind carrier.
Scheduled
9 min read By NT²
One sync hub for one vault identity
Tech
A vault does not need to enter a shared plaintext mailbox to sync. Its public cryptographic identity can name a dedicated edge coordinator that notifies replicas and points them to encrypted frames it cannot open.
Scheduled
9 min read By NT²
Blind replica sync on the edge
Tech
Sync does not have to turn a local vault into a cloud database. The edge can identify an account, store opaque replica frames, and deliver updates without learning what those updates contain.