Ask HN: Help With Network Filesystem Implementation
Hey Everyone,
I've been working on a syncing, network filesystem and I wanted to get your advice on an implementation detail. Our hope is that users will have all of their files (and eventually programs and settings) synced in the cloud.
Which would you prefer?
Option 1:
> You install our software, Skyline, on Device A
> We create a folder in your home directory, /skyline
> You select individual folders and tell Skyline to sync them
> Each folder you selected is accessible from both its original location, and from the /skyline folder
> You install Skyline on Device B
> A /skyline folder is added to home, and any folders you added from Device A are accessible
> You select individual folders and tell Skyline to sync them
> The folders you add are now accessible in their original location, in Device B's /skyline folder, and in Device A's /skyline folder.
Option 2: > You install our software "Skyline" on Device A
> Your entire home folder is now being synced
> You install our software, "Skyline" on Device B
> You are asked whether files from Device A should be merged with the files on Device B, or if the files from Device B should be deleted and replaced with the files from Device A
Thanks!PS: If you're interested, sign up for updates on http://www.projectmeadow.com
2 comments
[ 5.4 ms ] story [ 15.6 ms ] threadOh! This is for a laptop, not an app like the two I mentioned?
Our initial release will however be software that you can run on your current system.
> I don't understand how this is different? Option 1 sounds like MSFT SkyDrive and option 2 sounds like Dropbox. Just looking for what's different.
The cases being described in the post are _not_ the primary use case. Those cases describe users who aren't sure whether they wont to commit their entire system to project meadow integration.