tag:blogger.com,1999:blog-21033770.post3489858334927721038..comments2022-03-16T17:22:17.390+01:00Comments on transmissions from a free roaming agent of kaos: Nipping at Dropbox's heelsagentofkaoshttp://www.blogger.com/profile/01726092759041314700noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-21033770.post-42195266280736221852013-08-26T20:15:03.132+02:002013-08-26T20:15:03.132+02:00This just in from copy.com when I asked about how ...This just in from copy.com when I asked about how they managed sync conflicts between sync clients:<br /><br />"Unfortunately at this time, the user who syncs second would overwrite the changes by the user who syncs first. We're currently working on fixing this issue at this time."<br /><br />AT THIS TIME [2013-08-26] DO NOT USE COPY.COM SERVICE FOR ANYTHING MORE THAN A NETWORK agentofkaoshttps://www.blogger.com/profile/01726092759041314700noreply@blogger.comtag:blogger.com,1999:blog-21033770.post-43609241163337495062013-08-25T12:45:45.554+02:002013-08-25T12:45:45.554+02:00Just a word of warning on using the OS X sparse bu...Just a word of warning on using the OS X sparse bundle filesystem format approach. Here is something you don't want to see (example from filesystem contained in Dropbox):<br /><br /> ./Secured/SparseBundle/bands/11 (CompName's conflicted copy 2013-08-24)<br /> ./Secured/SparseBundle/bands/12 (CompName's conflicted copy 2013-08-24)<br /><br />I just happened to see the Dropbox agentofkaoshttps://www.blogger.com/profile/01726092759041314700noreply@blogger.com