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?
What I am confused by is what they think will happen to revenue. Step 1: "You can now use dropbox in fewer scenarios than before" Step 2: ??? Step 3: More customers paying more money Dropbox is paid for and used in various places I work and personally because of the Linux support. (Their competitors ignore Linux for some reason.) In my case step 2 is going to be them losing at least $1,000 in annual revenue. And they…
Ending support for Dropbox syncing to drives with certain uncommon file systems
221–230 of 429 posts
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#222Earlier quoted context omitted.
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.
> 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.
Individuals don't, but most individuals have no clue about the repercussions of hosting their plaintext data on Dropbox in the USA. Its a ticking timebomb.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#223Earlier quoted context omitted.
Home directory encryption via ecryptfs is now the default in most Ubuntu variants, and it would be insane not to attempt to support it. That said, given that my Dropbox subscription just renewed (and that Linux is pretty much the only reason I'm still using it, since there is no OneDrive client I can rely on), I am really sad this seems to be a future direction for Dropbox.
I get a terabyte free with onedrive, because of the office subscription. I wish I had a good way to utilize it on Linux.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#224No 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.
More seriously: Syncthing exists, and it is beautiful. I set my grandmother up with Synctrayzor and she doesn't know the difference between that and Dropbox. It is missing the ability to share things with a direct link, or share a repository or folder "easily" (read: in the same way it's done with Dropbox), but the trade off has been worth it for me.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#225Earlier quoted context omitted.
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.
> 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.
For example, if you have Synology or QNAP, there are packages to sync with cloud providers, like Backblaze B2, Amazon S3, Azure Cloud Storage, etc. So if one of your syncthing sync instances (which you can make with few clicks) is such a device, with few more clicks you can choose your cloud platform and backup to that.
Or you can be using something entirely different. That's the beauty, you can use whatever fits your needs and budget, you don't have to fit yourself to limitations of one or two pre-packaged solutions. You can do something entirely different, e.g. if someone from your family also has some NAS, you can backup to each others devices and not rely on third parties at all. The possibilities are limitless.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#226Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#227Earlier quoted context omitted.
What I am confused by is what they think will happen to revenue. Step 1: "You can now use dropbox in fewer scenarios than before" Step 2: ??? Step 3: More customers paying more money Dropbox is paid for and used in various places I work and personally because of the Linux support. (Their competitors ignore Linux for some reason.) In my case step 2 is going to be them losing at least $1,000 in annual revenue. And they…
Step 2: use the 20% developer manpower required to support filesystems used by 2% of the userbase to instead better support the other 98%.
Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#228Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#229Re: Ending support for Dropbox syncing to drives with certain uncommon file systems
#230Earlier quoted context omitted.
It's because Linux users know what they're getting and store more data then "regular" users. It's the same reason "unlimited" storage plans from Backblaze don't have a Linux client.
Those same Linux users know they can just download rclone which is the client that has support for backblaze ;)