by headgasket on 3/21/19, 10:39 PM with 35 comments
by theamk on 3/22/19, 3:44 AM
The way script works, it runs change monitor on both sides; if there is a change on local side, it will do local->remote sync; if there is a change on remote side, it will do remote->local sync.
This can go wrong in many, many ways. Here is the first example that came to my mind: you started a process on remote machine which creates lots of small files -- maybe extracting an archive, or generating images. So the syncer keeps syncing those files in remote->local direction. Meanwhile, you got bored watching the script and decided to edit some code. POOF! Any edits you make are continuously reverted.
Oh, and there is no error checking anywhere. Did your network had a hickup? Tough, we will march on anyway. Let's it was not in lines 101 or 104 -- if these commands have transient failures, then your newly made changes would just get reverted.
If you care about your data, please do not use this. Use anything else -- syncthing, osync, unison were named in this thread, they are all good.
by rasengan on 3/21/19, 11:37 PM
Amazing stuff. Brew, Cygwin and your favorite package managers have it.
by senorsmile on 3/22/19, 12:15 AM
by m-p-3 on 3/22/19, 2:10 AM
by systemspeed on 3/21/19, 11:55 PM
by orliesaurus on 3/22/19, 12:00 AM
by jasonhansel on 3/22/19, 1:27 AM
by mamcx on 3/22/19, 1:05 AM
by techntoke on 3/22/19, 12:29 AM
by etaioinshrdlu on 3/21/19, 11:10 PM
2. It doesn't actually replace Dropbox.
3. It does not seem very "viral" or income-generating. I know this is premature at this point, but without charging users for the service, is it reasonable to expect to make money off of this?
(Silly satire.)