The 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…
Ending support for Dropbox syncing to drives with certain uncommon file systems
201–210 of 429 posts
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#202Earlier 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…
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…
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#203Earlier quoted context omitted.
Yeah, this is probably about cutting out the big data users. They don't even offer an unlimited plan, but they probably noticed that certain linux users were using most of their 2tb plans while everyone else wasn't. Lose the most active users, keep the ones paying for something they don't need.
Dropbox for Business is unlimited, isn't it?
Why? Because there's always exceptions for 'abuse of service' and other exemptions.
The only time something is unlimited is if you do it yourself. Then you only have yourself to lean on.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#204Earlier quoted context omitted.
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
There has never been a network file system that really worked for this use case - detached operation by average users. The nearest we ever got was WebDAV.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#205It's a shame that btrfs seems to be dead in the water. I guess nobody with the resources to build such a filesystem actually needs its snapshotting and integrity features at the filesystem level?
Just because Red Hat marked btrfs deprecated on their systems, doesn't mean the technology itself is deprecated.
Also, from what I've read, they deprecated it because of resources issues rather than tech issues (seems like they had 0 btrfs devs and lots of XFS specialists on the team).
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#206Earlier 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
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#207For people looking to move to a service that supports Linux as a first class citizen: Mega works well enough as far as syncing files goes.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#208Earlier quoted context omitted.
But I (and I suspect quite a few other people) want a cloud backend to cover both the disaster-recovery cases and syncing while outside my LAN.
1) you can sync with a device inside your LAN, even if you are outside, with global discovery (enabled by default). 2) you can run your own off-site instance, that can be hosted with your favourite cloud provider.
How much would it cost to hire an admin to set up and maintain that instance?
The whole point of Dropbox is that I don't have to do any work.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#209Here is a direct link to the response from Dropbox: https://www.dropboxforum.com/t5/Syncing-and-uploads/Linux-Dr...
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#210Earlier quoted context omitted.
Completely agree. I'm not sure why someone would choose Dropbox over Keybase nowadays.
Continuity? I mean, does Keybase have a business model yet? Or is it still "$bigshot_vc who is friends with the CEO believes a few crypto/security gambles are in order"? Not meant critically, I love that they exist and found funding. It's just, as long as the model is "once the privacy shit hits the fan in some widely published scandal, we'll be the one that's ahead" there's only two outcomes: 1. It doesn't happen so…