Ending support for Dropbox syncing to drives with certain uncommon file systems
51–60 of 429 posts
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#52No 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.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#53The kicker is in the couching - dropping support for "uncommon filesystems" - of which their definition includes the default filesystem used by the most popular distro. Just dumb or wilfully ignorant?
With the fragmentation of Linux, even the "most popular" distro may hold a tiny market share. The guys at dropbox probably know far more about their users than what is reflected in some arbitrary popularity contest, so I doubt it's either ignorance or stupidity that led them to this decision.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#54This sounds fine to me. Ya'll are making sound like they're refuseing to sync because the FS is encryped. The file systems mentioned are really old. You can use newer FS's that are encrypted. They need to support extended attributes for obvious reasons.
Which one of these are old?
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#55Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#56No 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.
The modern alternative is probably Syncthing. I intermittently maintain a list of these things at https://github.com/pjc50/pjc50.github.io/blob/master/secure-... ; none of them have ever been precisely what I wanted. The cheap alternative to Dropbox with Linux support you want was "Hubic" from OVH (edit: now discontinued)
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#57Earlier quoted context omitted.
Just in case anyone doesn't recognize this quote, it is from the 2007 hacker news post about Dropbox: https://news.ycombinator.com/item?id=8863
It’s a really great example of worse is better.[1] We went from sophisticated network file system to a daemon that destroys your battery life (at least on Mac) watching for file changes in a directory. [1] https://www.dreamsongs.com/RiseOfWorseIsBetter.html
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#58The kicker is in the couching - dropping support for "uncommon filesystems" - of which their definition includes the default filesystem used by the most popular distro. Just dumb or wilfully ignorant?
Honest question, what do you believe is "the most popular distro"? Professionally, I have never seen a BTRFS deployment, nor any of the distros commonly at the top of Distrowatch (Manjaro, Mint, Elementary...). With the fragmentation of Linux, even the "most popular" distro may hold a tiny market share. The guys at dropbox probably know far more about their users than what is reflected in some arbitrary popularity co…
Edit: Actually I can't find that it was ever the default, but it was a pretty prominent option so I assume this decision is going to mess with a ton of customers.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#59I'm assuming encryptfs-ext4 has some attribute issue that prevents them for doing efficient deltas. That aside, what's the use case for encryptfs at all? Isn't it strictly worse than LUKS on the underlying volume or a volume file mounted via loopback?
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#60Dropbox isn't even the cheapest or best file syncing service, they're basically all a commodity at this point and if they don't want you as customers... just go elsewhere.