[acdha]

> Though this is not a phone app and Dropbox does have a history of mistakes causing data loss.

A history of random forum posters making huge assertions which inevitably turn out to be significantly overstated. It's trendy in certain circles to complain about Dropbox and the hype factor makes it easy to forget that for every person repeating anecdotes on HN there are a million normal people who use the service without issues.

[angry_octet]

As one of those 'random forum posters' aka Dropbox Customers who has lost data, I don't think it would be over stating it that I was fucking pissed off that my data was gone. I didn't really give a shit that other people were using the service without issues.

Its not rocket science to understand that a cloud data storage company is (a) going to have bugs, hence (b) data will be lost, and (c) customers will be dissatisfied.

The only saving grace for Dropbox is that the Google Drive windows client is a totally catastrophic data destroying pile of rubbish, and the Azure/Onedrive system is so microsofty and has no linux client either.

[acdha]

Again, there are people who've lost data and in some of those cases it was even caused by Dropbox — as opposed to the hardware failures or human errors which are often attributed to a service like Dropbox because that's what first made the problem visible — but that's still anecdotal rather than proof of widespread problem and, going back to the topic at hand, it doesn't tell us that the answer is to avoid installing updates. For a widely deployed consumer app, a significant fraction of the work will be defensive coding to reduce the impact of problems on the client and holding back updates will actually increase someone's exposure interval.