171–180 of 429 posts
Earlier quoted context omitted.
Just use syncthing. It works better, is open source, and runs on everything.
I guess you could say it runs of everything unless you use one of the two most popular operating systems in the world: Android and iOS.
Earlier quoted context omitted.
I’m not talking about FTP, which isn’t a network file system. I’m talking about NFS, AFS, and sucessors in that line of development. E.g. https://www.slideshare.net/mobile/snehcp/coda-file-system . I’m literally talking about the theory of the paper by Richard Gabriel ( https://www.dreamsongs.com/RiseOfWorseIsBetter.html ) which is that worse solutions often win because it takes too much time to bring a good solution…
> Which is why we’re all using an internet powered by Javascript, Electron apps on the desktop, etc. Worse is better. That's being a bit alarmist, isn't it? It's not worse is better. It's the right amount of compromises is better. Or, "good enough is better". Perfection usually has diminishing returns and is rarely obtainable. Worse is not better. Good enough is better; objectively so.
Earlier quoted context omitted.
In that case it might have been helpful if you stated that you were shifting the context away from FTP; as was the context in the GPs comment. ;) NFS and AFS (from what limited I know of it) are more designed for local networks thus to leverage NFS over a WAN you'd then need to tunnel your connection (eg via SSH or VPN). So while there is obviously overlap between them and Dropbox I wouldn't really say the two are al…
>you'd then need to tunnel your connection (eg via SSH or VPN) Well, there is an sshfs FUSE filesystem, for what it's worth
No problem, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem.
Earlier quoted context omitted.
Then put a limit and don't claim unlimited
Bad for business. Better slap "unlimited" everywhere but just shoo away the hoarders.
Earlier quoted context omitted.
Would you kindly provide recommendations? I'm looking for a sync service which can run on windows AND linux (which is why onedrive and google drive are out)...and i'm willing to pay a fair monthly fee.
rsync.net seems to get mentioned around here every now and again. I haven't used them though personally, so not sure of good/bad/etc. Unlike what their name (rsync) suggests, they do seem to support Windows clients and aren't *nix only: https://www.rsync.net/resources/howto/windows.html
1 - https://www.rsync.net/resources/howto/windows_backup_agent.h...
> we’re ending support for Dropbox syncing to drives with certain uncommon file systems . The supported file systems... and Ext4 for Linux. Yeah this is not how it works. This is not how any of this works
That statement is bit dubious. The next line also says: > A supported file system is required as Dropbox relies on extended attributes (X-attrs) to identify files in the Dropbox folder and keep them in sync. We will keep supporting only the most common file systems that support X-attrs, so we can ensure stability and a consistent experience. Certainly XFS supports xattr and hence ideally should be supported. I don't…
Earlier quoted context omitted.
FTP is neither sophisticated nor a network file system. Frankly I'd take Dropbox over FTP any day of the week - FTP needs to die. Thankfully your options are not limited to either Dropbox or FTP. Thus people who want simplicity can have Dropbox (or similar) and people who want control can have sshfs or any number of other tools out there that require some assembly but also don't suffer from the numerous problems that…
I’m not talking about FTP, which isn’t a network file system. I’m talking about NFS, AFS, and sucessors in that line of development. E.g. https://www.slideshare.net/mobile/snehcp/coda-file-system . I’m literally talking about the theory of the paper by Richard Gabriel ( https://www.dreamsongs.com/RiseOfWorseIsBetter.html ) which is that worse solutions often win because it takes too much time to bring a good solution…
Earlier quoted context omitted.
3G was when they added Windows support. Probably coincidence :)
No, Windows support came with the 2G in 2002. iTunes for Windows wasn’t a thing and few Windows machines had FireWire, but the Windows-compatible iPod came out in 2002. The 3G was the breakthrough model, but I lend that as much to the dock connector (which was available in USB and FireWire) and the growth of x-platform iTunes as anything. The broader point that it required Windows support for the iPod to become mains…
No problem, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem.
It is not like they are not implementing a feature but removing one.