Forum Discussion
Edge Dev Bookmark Sync change detection
HotCakeX, if you can point me to where on the edge://sync-internals/ I can see what Edge Dev thinks are duplicates would be cool.
So far I've tested the following steps:
1. completely deleted all bokmarks from Machine1
2. waited on Machine2 to see when the sync will happen, and indeed without prompting the process started and in the space of 2 hours all bokmarks save 1 have been removed from Machine2. Not 100% success, but ok for now
3. on Machine3 waited for a day to see the process start. I see that Machine3 has Transport State: Active and generally seems authorised to the sync server, but no cigar. Manual triggering or sync restart does not help. Went ahead and disconnected the user, deleting the bookmarks in the process.
4. at the same time, one day later, Machine1 somehow has recovered all deleted bookmarks. Also added a bunch of duplicate folders. Which is totally NOT OK.
So in 2 words: the entire sync system is a mess and seems in need to be disabled and developed from scratch. The current state is absolutely useless.
I will be looking at the Edge blog in hope that when they announce the next complete overhaul I can try it again.
Excuse my blunt description, but all these problems should have been caught during testing phase.
Further testing:
1. Went into my account and deleted a couple of defunct sync devices, bringing the total count from 10 to 6.
2. Logged out and back in Edge on Machines 1 to 3.
3. Deleted again all bookmarks (intentionally leaving only 2 so that we don't trigger some "no bookmarks found" recovery logic) - sync worked correctly and promptly. Good!
4. Imported bookmark backup from file - again sync was very fast, and correct so far.
As a side note, we talk Edge Windows + Edge Mac combination. Impressive.
So under lab conditions everything works. I'm quite certain that in a couple of days all bookmarks will be messed again, but let's see.
I would speculate that the problems with sync arouse because Chromium/Google constantly touches some of the bookmarks, thus messing their timestamps/IDs/whatever.
So I would guess the problem might not be with MS sync logic, but rather with Google's lax way with other people's data.
P.S. As you can see I'm VERY biased, but one of the reasons I love Edge Dev is that it gives us google-compatible (notice I did not say 'standards compatible'!) engine complete with MS data protection (honestly, I would trust MS over Google any day).