621–630 of 716 posts
Earlier quoted context omitted.
Even crazier is one drive has a limit on the total length of a file path, how is this even a thing that exists.
What do you expect to happen when your cloud storage file path is 5000 characters long and your local filesystem only supports a maximum of 4096?
Earlier quoted context omitted.
Even crazier is one drive has a limit on the total length of a file path, how is this even a thing that exists.
Unlimited strings are a problem. People will use it as storage. No, I'm not joking. We used to allow arbitrary paths in a cloud API I owned. Within about a month someone had figured out that the cost to store a single byte file was effectively zero, and they could encode arbitrary files into the paths of those things. It wasn't too long before there was a library to do it on Github. We had to put limits on it because…
Earlier quoted context omitted.
Even crazier is one drive has a limit on the total length of a file path, how is this even a thing that exists.
Everything needs limits otherwise someone will figure out how to or accidentally break it.
Avoid arbitrary limits on the length or number of any data structure, including filenames, lines, files, and symbols, by allocating all data structures dynamically.
Earlier quoted context omitted.
Bidirectional auto file sync is a fundamentally broken pattern and I'm tired of pretending it's not. It's just complete chaos with wrong files constantly getting overridden on both ends. I have no clue why people still use it and I'd cut my losses if I were you, either backup to the cloud or pull from it, not both at the same time like an absolute tictac.
I also have no clue why people use it. You can 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. From Windows or Mac, this FTP account could be accessed through built-in software.
We are going to drop blackblaze over this We discovered this change recently because my dad was looking for a file that Dropbox accidentally overwrote which at first we said “no problem. This is why we pay for backblaze” We had learned that this policy had changed a few months ago, and we were never notified. File was unrecoverable If anyone at backblaze is reading this, I pay for your product so I can install you on…
The deal was that Backblaze backs things up and I don't have to worry about it. Learning that it does not back things up is a punch to the gut. I am familiar with the exclusions and I have a look at that list to make I'm not missing anything from my backups. I had always thought the exclusions list was exhaustive.
Excluding other files and folders without telling me about it breaks the deal. Dropbox is important to several of the users I installed it for. Ignoring .git folders is another one that affects me and I had not known about. Ouch.
I will now have to look for alternatives. It has to be easy to install, run seamlessly on non-technical users' machines and be reliable.
I find it hard to be think of a worse breach of trust for a backup service than not to back up files!
Earlier quoted context omitted.
I think you might be confusing Backblaze reading files and how Dropbox/OneDrive/Nextcloud/etc. work. NC doesn't enable this by default (I don't think), but Windows calls it virtual file support. There is no avoiding filling the upload buffer, because Backblaze has zero control over how Dropbox downloads files. When Backblaze requests that a file be opened and read, Windows will ask Dropbox or whatever to open the fil…
No, I'm not confusing anything. Dropbox and onedrive can handle backblaze zipping through and opening many files. The risk is getting too many gigabytes at once, but that shouldn't happen because backblaze should only open enough for immediate upload. If it does happen it's very easily fixed. If it overloads nextcloud by hitting too many files too fast, that's a legitimate issue but it's not what OP was worried about…
as well as giving users the rightful choice about such things
bad call
Backblaze is such a weird case. On one hand, it became the most trusted personal backup provider on reddit and HN, on another - their software is absolute junk, and as some comments in this thread are highlighting - even their restore can't be trusted. I've never needed to restore anything, so can't say anything about this, but once, one of my devices deleted a file in Syncthing, and I went into Backblaze to see if t…
I guess the problem with Backblaze's business model with respect to Backblaze Personal is that it is "unlimited". They specifically exclude linux users because, well, we're nerds, r/datahoarders exists, and we have different ideas about what "unlimited" means. [1] This is another example in disguise of two people disagreeing about what "unlimited" means in the context of backup, even if they do claim to have "no rest…
Any company that does the "unlimited*" shenanigans are automatically out from any selection process I had going, wherever they use it. It's a clear signal that the marketing/financial teams have taken over the businesses, and they'll be quick to offload you from the platform given the chance, and you'll have no recourse. Always prefer businesses who are upfront and honest about what they can offer their users, in a s…
This article answers the question, "What does Backblaze back up?" Backblaze backs up all of your data across all of the user profiles that are on your computer as soon as you install the client.
Backblaze believes that you do not need to worry whether you selected all of the files that you care about, put any files in a different location on your computer, or added new files that may not be included in your online backup. Therefore, Backblaze automatically selects all of your data.
This is at best flat out wrong, at worst a blatant lie. But this was what I thought I was buying and paying for. Turns out you do have to worry!
Don't lie about other stuff you don't back up. Very disappointed in Backblaze.