|
|
|
|
|
|
by howellnick
4534 days ago
|
|
|
He's not even sure that Chrome.exe was at fault. Why are you so quick to assume that it's Backblaze's fault in this one customer instance? He could have just reinstalled his machine, did a lot of weird configurations, etc. and not have even rebooted his computer a single time yet. Anyway, my point is that there is a lot of missing variables and information to make such assumptions. The customer is _not_ always right, you know. |
|
|
The first issue (downloads not working) was on an otherwise-fine laptop that I checked to ensure could do other bandwidth-sensitive tasks (streaming HD video, etc.) it was only the Backblaze site and downloader that showed 0-3kb/sec and then failed.
I could have done a lot of weird configurations, but just to be clear, in this situation, I did not. On the first download that didn't work, I was restoring to a laptop that I had just booted up and had not performed any configuration on. In the second case, I was downloading a 6GB file to newly restored system that I'd rebuilt from scratch, and I'd tested all of the components (including the network connection, disks, etc.) prior to considering the rebuild complete. After that and all of the updates, it had run in a stable condition for some time before I attempted the download.
I agree that the customer is not always right. But also note that I am not claiming that backblaze is evil. I'm claiming that this process and my experience makes me question their model as well as my own idiocies.
And I also should note that while I might not seem that adept in this scenario, I've spent years as an IT support person, systems administrator, and developer. Which is not saying I'm right all the time or to bolster my case, just to note that I didn't do _no_ troubleshooting before I wrote the post.