Works as advertised. The advantage of this program is that it syncs just about anything that you can sync through .Mac, including contacts, bookmarks, etc. It also has a good user interface.
That said, I prefer address-o-sync for syncing addresses. MySync uses Apple's sync engine. It will inform you if information on cards conflict, e.g., if they have the same work number. However, if information is unique to one card or the other, it assumes that you want to keep it and merges the cards. This can result in bad info. For example, if suppose that the old card for John Doe on machine A has work number 123 and mobile number 456. John Doe has moved, and machine B has a new work number 789 and no longer has his mobile number. When you sync, Apple's engine will inform you of the conflicting work numbers, but will assume, because it's unique to one card, that you want to keep the mobile number, even though it's bad.
On the other hand, address-o-sync gives you three options when any information conflicts on the card: Keep the old card, keep the new card, or merge. It's more flexible, and prevents re-importing bad data. In the example above, I could view the card on both machine A and machine B and reject all of the data from machine A, preventing the bad mobile number from surviving.
Doesn't seem to work. I installed it under Mac OS X 10.4.5. The first time I ran it, when I tried to save the list of blocked sites, it asked me for my administrator password multiple times and never was able to authenticate, even though I'm positive that I was typing the correct password. I quit the program, re-launched it, and it would not relaunch because my etc/hosts file had been deleted. Something is very wrong here.
[Version 1.1b]
Please login or create a new MacUpdate Member account to use this feature
Decompose
Tc_ rated on 02 Dec 2010
[Version 1.1]
SyncTogether
TC_ reviewed on 25 Nov 2006
That said, I prefer address-o-sync for syncing addresses. MySync uses Apple's sync engine. It will inform you if information on cards conflict, e.g., if they have the same work number. However, if information is unique to one card or the other, it assumes that you want to keep it and merges the cards. This can result in bad info. For example, if suppose that the old card for John Doe on machine A has work number 123 and mobile number 456. John Doe has moved, and machine B has a new work number 789 and no longer has his mobile number. When you sync, Apple's engine will inform you of the conflicting work numbers, but will assume, because it's unique to one card, that you want to keep the mobile number, even though it's bad.
On the other hand, address-o-sync gives you three options when any information conflicts on the card: Keep the old card, keep the new card, or merge. It's more flexible, and prevents re-importing bad data. In the example above, I could view the card on both machine A and machine B and reject all of the data from machine A, preventing the bad mobile number from surviving.
loopBlock