One profile, one launch
If a computer goes silent for 2 minutes, the lock is released and the last uploaded version wins.
One profile, one launch. A second launch is refused until the first one closes the profile.
The app takes the profile lock and downloads missing blocks.
While the profile is open, the app renews the lock every 15 seconds.
Changed blocks are encrypted and uploaded, then the lock is released.
The profile opens with the same cookies and localStorage.
Files are split into blocks, encrypted with the profile key, addressed by hash and never duplicated.
If a computer goes silent for 2 minutes, the lock is released and the last uploaded version wins.
Only an encrypted block cache remains. The app gets its key only while access is active.
If an upload fails, the app retries in the background and holds the lock until it’s done.
Caches and engine service folders are left out of sync, so profiles move faster.
The second one is refused: the profile is busy until it’s closed and the changes are uploaded.
In server storage as encrypted blocks. Encryption happens on your computer, with the profile key.
The app retries the upload in the background. The lock is held until the changes are uploaded.
No. The local copy is wiped after closing, and the block cache can’t be decrypted without access.