23. Sync copies only the changed chunks
Sync keeps a local and a Peergos folder the same in both directions, sends only changed chunks, treats deletes as a choice, serves many devices, and since 2025 unrelated concurrent writes no longer fail (same-file conflicts remain conflicts).

23. Sync copies only the changed chunks

Sync keeps a local and a Peergos folder the same in both directions, sends only changed chunks, treats deletes as a choice, serves many devices, and since 2025 unrelated concurrent writes no longer fail (same-file conflicts remain conflicts).

It is the everyday feature that the chunk model makes cheap.

Sync keeps a local folder and a Peergos folder the same. Both directions.

Change a big file, and only its changed chunks are sent. The rest of the file stays where it is.

Deletes can follow in either direction, or neither. You choose.

Several devices can sync the same folder. A laptop, a desktop, a phone, each holding a copy.

Two devices write different files at once? Since twenty twenty five, that no longer fails. The same file changed in two places is still a real conflict.

Check yourself. A 1 GB file gets one byte changed. What is sent? And what still counts as a conflict?

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Connections0

Connections show where other documents or comments link to this document.

Related documents

Loading connections…