b according to a synchronization log 160 the synchronization log 160 itself periodically can be size limited according to the operation of a coupled garbage collector 170 as an example the synchronization log 160 can include a difference log of previously omitted updates such that modifications to a synchronization filter during synchronization will not result in redundant updates as another example the synchronization log 160 can include a peer synchronization log of updates provided by peers synchronizing with one of the clients 120 during synchronization updates provided by the peers can be expressly excluded from the updates applied during synchronization updates received from a peer that are not reflected in the data store of synchronized data 130 a however can be included during synchronization fig2 is a flow chart illustrating a process for difference log driven data synchronization the process can begin in block 210 at the start of a synchronization operation with a specified client in block 220 an initial set of updates can be computed based upon data that has been changed data that has been added and data that has been deleted since the conclusion of the immediate past synchronization operation in block 230 the initial set of updates can be filtered according to a synchronization filter notably in block 240 a difference log can be retrieved including a listing of updates that had been previously filtered out of an initial set of updates according to a synchronization filter in block.