6,765 karma · joined January 2, 2016
You may or may not be acting as an apologist for the sleaziest, worst industry on earth here, but you certainly sound like it, even if it is unintentional. As this is hacker news, P(makes money working for sleazy, terrible companies) is high so you'll have to accept this obvious interpretation.
Look, I actually kind of agree with you, but social media _already has all the PII_ to an extent unparalleled in history. Come on. "We have to wonder what the motivation here is"?
I think the world is much, much more varied and complex than these "this is the one true doom" mindsets can fathom. It's a constructed theory that makes perfect sense until it meets the real world.
Frankly as I am aging myself and noticing a lot of changes to recovery time and overall physically feeling good, I can totally understand getting on testosterone, for example, but random peptides that show up in white bags from random Chinese labs? no.
>NOTE: >iCloud's most recent update prevents Backblaze from backing up files that iCloud synced. >To back up these files, download them to another local location where Backblaze can read them.
So which is it?
Is icloud drive backed up or not? Please be clear. Which versions support this?
https://www.backblaze.com/computer-backup/docs/back-up-iclou... still says that it no longer backs up icloud drive files. Then it gives directions on how to back them up. Which is it?
Also, why did you stop backing up .git folders, sliently?
This case, and a bunch of the others, are variations on failing to correctly implement dependency analysis. I'm not saying it's easy, it is far from easy, but this has been part of large systems design (anything that involves complex operations on trees of dependent objects) for years, especially in the networking space.
Indeed, your fourth bullet gets to some of the very ancient techniques (though STP isn't a great example) to address parts of the problem.
The last bullet is very hard. Honestly, I'd be happy if icloud and dropbox just got the basics right in the single-writer case and stopped fucking up my cloud-synced .sparsebundle directory trees. I run mtree on all of these and routinely find sync issues in Dropbox and iCloud drive, from minor (crazy timestamp changes that make no sense and are impossible, but the data still complete and intact) to serious (one December, Dropbox decided to revert about 1/3rd of the files to the previous October version).
The single writer case (no concurrency, large gaps in time between writers) _is_ easy and yet they continue to fuck it up. I check every week with mtree and see at least one significant error a year (and since I mirror these to my NAS and offline external storage, I am confident this is not a user error or measuring error).