>
> I know that Firefox keeps many bookmark backups and will restore them in
> some cases (eg, on a corrupt places.db) - so it seems possible that
> something unrelated to Sync went wrong initially and Firefox made an
> attempt to recover bookmarks, which caused Sync to delete the server copy
> of all bookmarks and re-upload the restored set. If that restored set was
> incomplete, the other devices then also got that incomplete set and
> everyone was sad - it seems possible the server copy of the bookmarks could
> be better than the restored set making the Sync behaviour simply wrong
> here, but it's difficult to speculate about what is actually happening.
For the record, note that a DELETE will remove records from the server, but
not delete bookmarks from other devices — to do that they'd need to be real
records containing {deleted: true}. What might have happened here:
* The client wiped the server.
* The client uploaded a subset of the user's bookmarks, including folders.
* Other clients downloaded those records and made their local databases
match.
I would be surprised if this somehow deleted local unmentioned records.
Sync might have moved the old children to Unfiled Bookmarks.
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
