Live data from Hacker News

Backblaze Privacy Update: Third-Party Tracking

backblaze.com

51–60 of 72 posts

Re: Backblaze Privacy Update: Third-Party Tracking

#51
Looking at this submission, comments and its ranking here, I’m sure that nobody from Backblaze will comment here or on HN for some more time. This blog post makes it seem like an internal gag order has been imposed. Some hand wavy updates are what we should expect I suppose.

The post title is also dishonest in saying third party tracking and not adding details — this is Backblaze that intentionally and explicitly shared sensitive data with third party tracking. It’s not as if some third party tracked Backblaze’s paying users surreptitiously.

This response is actually helpful for the competition as far as the HN audience is concerned.

Edit: I’m really curious on the extent of coverage of this issue. I searched online and found only mjtsai.com and theregister.com covering this sensitive information leak. Are there any other major tech sites that have covered it so far?

Re: Backblaze Privacy Update: Third-Party Tracking

#53

Anyone got any alternatives?

Many of them in the previous post about this subject.

After reading / comparing prices, for my needs I ended up with:

- OVH Cloud Archive: 0.0023/GB for cold storage + incoming/outgoing prices. https://www.ovhcloud.com/en/public-cloud/prices/#storage

- iDrive: $ 69.50/5TB/year https://www.idrive.com/pricing

- Wasabi: $5.99 / 1TB/month: https://wasabi.com/cloud-storage-pricing/#cost-calc

Re: Backblaze Privacy Update: Third-Party Tracking

#54
I expect zero http requests to any Facebook servers when I visit anycorp dot com and that’s regardless of whether I’m a paying customer or logged in user. If any actual data is transferred that’s even worse, but already having a connection to Facebook via a tracking pixel for “audience building” or similar is over the line already.

Re: Backblaze Privacy Update: Third-Party Tracking

#55
post #6

They literally sent file names and file sizes over to Facebook. That might very well include very personal or confidential data. The fact that they don't even mention this and make it sound like some random unimportant tracking happened without them noticing is completely ridiculous.

The part I don't understand is how exactly does a tracking pixel end up collecting filename information?

Re: Backblaze Privacy Update: Third-Party Tracking

#56
post #6

They literally sent file names and file sizes over to Facebook. That might very well include very personal or confidential data. The fact that they don't even mention this and make it sound like some random unimportant tracking happened without them noticing is completely ridiculous.

The part I don't understand is how exactly does a tracking pixel end up collecting filename information?

Because it's a script that examines the DOM and ships the information from the page to facebook for analysys.

Re: Backblaze Privacy Update: Third-Party Tracking

#57

Yeah. Backblaze are addressing this "blunder" only because they got caught. Not because they give 2 shits about their customer's privacy. The smug tone in this joke of a response to the issue proves this.

Man, your distrust seems toxic to me. The simplest explanation is they goofed as they admitted, if they were malicious, they'd upload those file names from their server straight to FB's, not through your god damned browser.

And of course they only addressed it after they "got caught", they didn't know about their fuck up before that, if you want to sneer at them, sneer at them for not being careful enough to let this happen, not what you wrote.

I'm not trying to defend them, more like I want to protest against ungrounded casual insulting bashes like yours that seems way too freaking common nowadays. I do think they care about customer privacy, because it affects their income. (Admiteddly they were too casual about it, they were still partnering with Facebook...).

Re: Backblaze Privacy Update: Third-Party Tracking

#59

Earlier quoted context omitted.

The part I don't understand is how exactly does a tracking pixel end up collecting filename information?

Because it's a script that examines the DOM and ships the information from the page to facebook for analysys.

How do we know it did this? They didn't say so

Re: Backblaze Privacy Update: Third-Party Tracking

#60

Earlier quoted context omitted.

Because it's a script that examines the DOM and ships the information from the page to facebook for analysys.

How do we know it did this? They didn't say so

Here's the screenshot: https://twitter.com/Benjojo12/status/1373707799054712836
Post reply on HN