Opera Sync and Account Backend: Conflict Resolution for Concurrent Offline Modifications

Synchronization State Consistency

Opera Sync implements an end-to-end encryption model to synchronize profile data, including bookmarks and history, across desktop and mobile clients. The system typically employs a timestamp-based priority mechanism to resolve conflicts between the local client and the cloud-based backend.

Offline Modification Boundary

A specific challenge arises when multiple devices modify the same bookmark folder structure while offline. Upon reconnecting to the Opera Sync account system, the browser must reconcile these divergent states. While the general behavior favors the most recent timestamp, the deterministic outcome for nested folder modifications remains unclear.

Given the current synchronization protocol, what is the expected behavior when two devices create different sub-folders within the same parent directory while offline? Does the system merge these additions, or does the latest timestamp overwrite the entire folder state?