So, to be perfectly clear, it is more than possible for you to sync the photos from your computer, hit the "backup now" button, have Backblaze respond back that a backup is complete, and then find out that all of those photos you thought you had backed up were not there.
All of this to make it look like your application is performing better than it actually is.
On top of that you keep doing that infuriating thing where you ignore what people are saying and respond as if they're idiots or by trying to deflect the issue. No one expects you to run when the computer is off, and pretending like that's what's being said is downright insulting. What they do expect is that hitting the "backup now" button, and having your application respond that their files have been backed up, should actually mean that the files are backed up.
The more you talk the more you try to twist this around into something it's not- a visual glitch, misreading your policies, or people turning their computers off when they shouldn't- rather than trying to understand why your customers are upset and actually deal with it. That's why this issue has grown, and why we keep having these conversations- you guys have zero concept of responsibility and would rather insult your customers than actually make a viable product.
No, we should display the last time you were fully backed up in the console. If you turn on your computer, move photos to it, and turn it off, even if you press "backup now" likely they won't be included in the scan. In our best practices and introductory email we say that if you want at least a "daily" backup, you have to let us run for at least 3 hours so that we can fully index your new/changed files and back them up. If you added a lot of files it'll take longer, if you only add a few, it can be pretty quick.
If your complaint is that the Backup Now button does not do a full-system scan, that is totally valid and after the reddit thread our engineering folks are looking in to changing the "backup now" button's behavior. One of the reasons it doesn't do that now is because a full-scan will hang your system, where uploading the remaining files is very light and unnoticeable. Like with any functionality decision it's tough to say what is the best answer, hanging someone's system each time they press a button, or kicking off a remaining files upload and gradually scanning the drive over the next hour.
I sincerely apologize if I am not communicating well though, I am not trying to talk down or assume you or anyone else is an idiot in any way. I've tried to address everything that you bring up on here and on reddit. As far as expecting Backblaze to run when the computer is turned off, you'd be surprised at how many of our support tickets ask, "If my computer is off, are you still working?" so we do see that quite a bit. I don't bring it up to try and dig at anybody. I also think we've taken responsibility for the bug that mislead you in to believing you had data on our system when it had already been removed. Once we realized what had happened in your case we offered a refund and have since fixed it so that it does not happen to anyone else.
We're in the business of backing up data. When customers lose data, whether it's something they did or something that occurred on our end, we feel badly about it and try to make it right. We do have a viable product. We've restored over 4 billion files for the customers that have accounts with us. We take it very seriously.
All of this to make it look like your application is performing better than it actually is.
On top of that you keep doing that infuriating thing where you ignore what people are saying and respond as if they're idiots or by trying to deflect the issue. No one expects you to run when the computer is off, and pretending like that's what's being said is downright insulting. What they do expect is that hitting the "backup now" button, and having your application respond that their files have been backed up, should actually mean that the files are backed up.
The more you talk the more you try to twist this around into something it's not- a visual glitch, misreading your policies, or people turning their computers off when they shouldn't- rather than trying to understand why your customers are upset and actually deal with it. That's why this issue has grown, and why we keep having these conversations- you guys have zero concept of responsibility and would rather insult your customers than actually make a viable product.