News for hackers. Stuff that matters.
Re:Firefox 57 delays requests to tracking domains by codezero on Tuesday December 19, 2017 @05:59PM (#15965250)
I work for an analytics company, this will affect my snippet – I don't think it is a big deal, but I'm going to benchmark it on a few sites. From what is described here, it may actually help us. When folks throw tons of tags into their site, we're all competing against each-other as well as the site's own loading – it makes sense to prioritize the site's rendering.

I think of this as no more invasive than pre-caching stuff in a page when you see links that are likely to be clicked, or any other browser optimization.

I may be pounding my fist later if the results don't look great, but ultimately, I think Mozilla's heart is in the right place.

I can think of tons of ways to work around this if I thought it was a real issue, I don't. People who want to block analytics, trackers, ad networks, etc... know how, and this doesn't feel like it is targeted at those people, or even squarely at the tracking pixels.

HN-pre-emptive-defend-myself: My company doesn't share or sell data with third parties (it's in our TOS – and could obviously change in some Orwellian future, but we'd have to update the TOS), it's the customer's data, they can use it in the same way they'd use any other data they collect. We don't do cross-domain tracking, or aggregate behavioral information across customers, and the way we've built it, it makes it pretty hard to tie any two visitors together across sites if you were to hypothetically acquire our dataset. We're also working on building tools to comply with GDPR and wipe out data per-request. Anyways, I think a lot of very bad actors have made the space have a bad reputation and I don't blame anyone for blocking everything, or even for hating my company, or generally all analytics.

Re:Firefox 57 delays requests to tracking domains by notyourday on Tuesday December 19, 2017 @08:18PM (#15966140)
> My company doesn't share or sell data with third parties (it's in our TOS – and could obviously change in some Orwellian future, but we'd have to update the TOS), it's the customer's data, they can use it in the same way they'd use any other data they collect. We don't do cross-domain tracking, or aggregate behavioral information across customers, and the way we've built it, it makes it pretty hard to tie any two visitors together across sites if you were to hypothetically acquire our dataset.

Are you the CEO and do you currently own controlling interest? Because if not, then everything that you are saying is worth about as much as a slice of pizza someone dropped in the NYC subway.

Re:Firefox 57 delays requests to tracking domains by codezero on Wednesday December 20, 2017 @12:30AM (#15967253)
Nope, happy to fall on a sword if this happens though.

Also – really bummed you got downvoted – this point is very valid and other folks in my position should take note.

Re:Firefox 57 delays requests to tracking domains by notyourday on Wednesday December 20, 2017 @08:05AM (#15969157)
@codezero, my point was not about falling on a sword. Rather it was that NH has this extreme naivete related to statements coming from those that do not have any real say.

How many people here think that data is removed from BI data lakes when a user deletes the account ( or at +N months )?

[Edit: Downvotes on this one also?]

Ask what happens to customer's data used by business intelligence when customer deletes the account in your company. Do it in email so it is in writing. It would be extremely illuminating.

Ask if what when a customer or your app acting on a behalf of your customer executes a DELETE against your API your API deletes the record or:

1) sets a deleted_at to now which your ORM treats as "deleted"

2) send a message to a queue (Customer XYZ deleted record P) which has multiple subscribers, one of which executes a deletion while the other one dumps the new state into a BI lake/archive dataset/what-if-a-customer-comes-back-would-not-we-want-to-be-able-to-give-them-all-their-data-back database?

Re:Firefox 57 delays requests to tracking domains by codezero on Wednesday December 20, 2017 @10:37AM (#15970427)
I get where you are coming from but you are also making some assumptions that are a bit broad. It’s a laudable goal to educate naive folks on HN, I support you in that, but you should try a different approach.

I’m not naive. I’ve been working in tech since 1996 when I managed a dial up ISP. I worked at Red Hat the day they IPOed and have been with Heap for almost four years. I was employee number 8, and personally wrote much of the code to remove data from our databases.

We have strict controls and logging around who can access our infra, as is necessary for SOC2 compliance. We have rolling backups (that are read only except by very specific individuals) so even if I got real mad one day and decided to ruin my career, we could restore the data, however, we don’t keep backups indefinitely so when data is deleted or removed with intent, it will eventually be gone in backups too.

I’m not on the board, but I do have influence as I am the head of our solutions and support team. I am a privacy advocate and take a firm stand on protecting my customers’ data and executing their own desires to protect their customers, and I do my best to not only instill these things in my team and company, but also to make policies and controls to make them real.

When I delete data, I don’t rely on a message being sent to a queue. I do not “soft” delete. When our customers ask for their data to be deleted, we delete it without delay.

I will say that sending a message in a queue would be pretty efficient and if we went that route I’d have the consumer of that message verify that the data was deleted.

Ultimately our backing store is Postgres, it’s not rocket science to understand how deleting that data works, we could get into a discussion about how it’s not really deleted until it’s been reallocated, at the DB and at the OS and hardware levels, but I don’t think you’re trying to make that argument.

Is everything perfect? No, that would be naive to say, but we don’t assume it is and work hard to remain accountable.

I’m happy to discuss this or about anything else here or over email, Skype, hangout, in person, etc, but I do want to say that you should challenge your own assumptions a bit more. Not every person or company is inherently bad, naive or ignorant. A lot of people on HN are extremely tenured, bright, and thoughtful, they just usually know better than to comment here, if anything, that is my most naive action.

Re:Firefox 57 delays requests to tracking domains by notyourday on Tuesday December 19, 2017 @10:14PM (#15966728)
Jesus. Really? Downvotes? Pretend this person worked for facebook and made some statement regarding what the company does.

(a) he would be fired on the spot by the company itself ( as he is not authorized to speak on behalf of the company )

(b) he would be laughed out the room because he does not control company decisions

The same applies to every single company. Every single one.

Re:Firefox 57 delays requests to tracking domains by codezero on Wednesday December 20, 2017 @12:33AM (#15967266)
Agreed, they make a good point, however, I think the terms of service are binding, and if what we're doing changes, we _must_ update them. This, of course, does not change the fact that we've collected a lot of data and it would suddenly fall under the new terms of service.

With that said, I actively delete customer data on request, and a terms of service change like this _might_ (very reasonably) prompt someone to request their data to be deleted, and since terms of service are not typically immediately effective without consent, I feel strongly that I would make sure I could remove data for people who do not agree with the new terms of service. What I'm saying, is that I would fight very hard for my customers, like, ridiculously hard.

As said above – I am not the CEO – I don't have controlling interest, and there is absolutely some future where the things I said above are impossible to execute. I have not felt that way yet, and I am very conscious of the possibility if that in the future, and will stay vigilant both for my customers and for my own peace of mind to make sure we're always doing the right thing.

Re:Firefox 57 delays requests to tracking domains by j_s on Wednesday December 20, 2017 @05:36AM (#15968500)
Yes, since new ToS have always been retroactively applied to all previously collected data they offer zero privacy protection over the long term.

Google Has Dropped Ban on Personally Identifiable Web Tracking | https://news.ycombinator.com/item?id=12760003 (October 2016)

An effective opt-out may help most of the vigilant, but it is in the best interest of those changing the ToS to keep it as confusing/hush-hush as possible.

Re:Firefox 57 delays requests to tracking domains by arkh on Wednesday December 20, 2017 @03:32AM (#15967966)
I'll have a wild guess there: all devs and most managers have access to the full data set. Any disgruntled one could ex-filtrate it anywhere with not trace.

That's the kind of things which make me for the vision of data as liability.

Re:Firefox 57 delays requests to tracking domains by codezero on Wednesday December 20, 2017 @10:49AM (#15970547)
Absolutely not. We have strict control over our data and access to infrastructure.

Every person with access can only get it via a bastion VPN with their own key. Access is logged to an external host which they do not have access to. We are SOC2 compliant (just waiting on final certification) and we have regular pen tests both against our code as well as our employees with mock phishing.

As a total aside: it would cost a serious amount of money to exfiltrate the data in bulk, and would cause an obvious strain on our infrastructure. Assuming they get by all the above protections, and are really clever, sure, never say never, but I think we can not assume the worst but prepare for it none the less.

Re:Firefox 57 delays requests to tracking domains by walshemj on Wednesday December 20, 2017 @07:49AM (#15969072)
They should have internal security teams that monitor this
Re:Firefox 57 delays requests to tracking domains by notyourday on Wednesday December 20, 2017 @08:06AM (#15969166)
Damn it. You owe me a new keyboard.
Re:Firefox 57 delays requests to tracking domains by mquander on Tuesday December 19, 2017 @11:46PM (#15967120)
I have no idea what you're talking about. People from big tech companies say their opinion about what their company does all the time.

Your comment was super rude.

Re:Firefox 57 delays requests to tracking domains by notyourday on Wednesday December 20, 2017 @08:08AM (#15969173)
Really? People at Google say that they know what Google does with data?!
Re:Firefox 57 delays requests to tracking domains by frik on Wednesday December 20, 2017 @01:23AM (#15967474)
You are right. But speaking out the truth isn't compatible with HN users as of late. So see downvoting and getting flagged as a sign you are right, just the other try to hide your post and keep you from posting. Unfortunately the atmosphere got really toxic, with many things got hidden from users, the down-voting/flagging does no good.
[dead]
Re:Firefox 57 delays requests to tracking domains by codezero on Wednesday December 20, 2017 @12:49AM (#15967341)
I get what you're saying, but I also want to assert: we're not in the thieves' guild. I mentioned that analytics as a broad category, gets bunched up with a bunch of very nefarious folks – it's like conflating Tor to The Silk Road and their ilk (of which I have no strong objection, but I am using as an example, since many might see selling drugs as "bad", but Tor as "good").

With that said, the comments above this thread, which point out that I have little control over our "Tor" becoming "The Silk Road" are valid and are often on my mind, and I can only say that I will not go gentle into that good night, if it does come to pass.

Re:Firefox 57 delays requests to tracking domains by quickben on Wednesday December 20, 2017 @04:08AM (#15968117)
Unfortunately for the field , analytics is equated with advertising and user profiling lately.

We'll see how this one pans out, but it may be somewhat career limiting.

Re:Firefox 57 delays requests to tracking domains by codezero on Wednesday December 20, 2017 @11:44AM (#15971159)
In fairness, much of the modern data analytics field was born out of the need to quantify advertising effectiveness, so I'm not surprised the two have become conflated.

Google Analytics is (mostly) free in part because it supports and validates users of Adwords, and this has contributed heavily to the ubiquity of GA.

Re:Firefox 57 delays requests to tracking domains by Dylan16807 on Wednesday December 20, 2017 @12:29AM (#15967252)
notyourday is insulting the guy based on a supposed lack of "authorization" to speak. That has absolutely zero to do with ethics of the company or the contents of their post.
Re:Firefox 57 delays requests to tracking domains by notyourday on Wednesday December 20, 2017 @06:16AM (#15968676)
When pointing out that the king is naked is considered an insult to and by the people clapping about those amazing invisible clothes, one needs to seriously examine if he or she wants to be the person clapping
Re:Firefox 57 delays requests to tracking domains by Dylan16807 on Wednesday December 20, 2017 @04:27PM (#15973980)
Naked vs. amazing clothes. Note that those are the same topic, and conflict with each other.

But what you did was the equivalent of shouting someone down for not being the king. You weren't calling codezero wrong, you were saying they weren't in charge.

When they're merely reporting the policy, who cares if they're the one in charge?

Hell, the logic of "mock the guy for not being in charge" would apply even if they were also calling the king naked! That should show how flawed it is when compared to your actual goal of... being anti-tracking or something?

Re:Firefox 57 delays requests to tracking domains by dsr_ on Tuesday December 19, 2017 @06:22PM (#15965441)
A couple of years ago I went to a conference where one of the speakers outlined his company's web page optimization methods. The big one was to delay executing JS until at least the visible page content was loaded, and all JS that actually implemented customer-useful bits.

His example page loaded 94 scripts, which he claimed was representative of many pages.

Re:Firefox 57 delays requests to tracking domains by megaman22 on Wednesday December 20, 2017 @03:07AM (#15967875)
> His example page loaded 94 scripts, which he claimed was representative of many pages.

I know this is the norm, but can we just agree that this is insane?

Some sites I go to, I just see the block badge on UBlock Origin ticking up like a Bitcoin price tracker.

Re:Firefox 57 delays requests to tracking domains by MaxBarraclough on Wednesday December 20, 2017 @06:04AM (#15968628)
> ticking up like a Bitcoin price tracker

Fitting comparison - we can also expect performance degradation similar to Bitcoin's.

Re:Firefox 57 delays requests to tracking domains by smsm42 on Wednesday December 20, 2017 @04:17AM (#15968157)
One of the consequences of installing Ghostery was that it shows a counter of how many scripts are loaded on the page. Turns out I have severely underestimated how many scripts average site loads - and I work in the industry!

As an example, I just loaded CNN site - it has 28(!) trackers and uses 38(!) different domains. And that's a low number because some of these scripts would load other scripts if I enabled them to run...

That's a super-mainstream site, imagine how many more shady ones have.

Re:Firefox 57 delays requests to tracking domains by cyborgx7 on Wednesday December 20, 2017 @06:42AM (#15968775)
I'm looking forward to the EU regulations kicking in and you having to get consent from everyone ou save data on.
Re:Firefox 57 delays requests to tracking domains by Ygg2 on Wednesday December 20, 2017 @07:10AM (#15968909)
Do you agree for us to save your data?

[Yes] [Read more]

Re:Firefox 57 delays requests to tracking domains by ainiriand on Wednesday December 20, 2017 @08:04AM (#15969153)
The other option, Closes tab, is simply not gonna happen so why annoy the user.
Re:Firefox 57 delays requests to tracking domains by bigbugbag on Wednesday December 20, 2017 @09:28AM (#15969746)
legal obligation.
Re:Firefox 57 delays requests to tracking domains by jamesfe on Friday December 22, 2017 @03:56AM (#15986151)
I'm not sure why you feel the need to defend yourself. HN has a low opinion of the concept of selling user data, but in practice, there are plenty of ad-supported startups represented here.

Google is selling your data to marketers. Facebook is one giant data-collection/data-sales empire. In theory, the HN collective hates data selling, but in practice, they love the companies that are doing it and their products.

I find it ironic that I come here and see people worshipping the big adtech companies and their tech but then when someone posts a comment about not selling user data, a thousand tin-hat naysayers jump out of the woodwork to flog them to death.

It's OK. It's why I can read the NY Times and a thousand other online newspapers - FOR FREE. It's why I can go to Google and type in "why does my butt burn when I poop" and get an answer - FOR FREE. It's why I can use dozens of adtech and user-data-supported services - FOR FREE. I pay for those things with data about me, my habits, and my browsing history.

Re:Firefox 57 delays requests to tracking domains by j_s on Wednesday December 20, 2017 @01:41PM (#15972447)
I appreciate your willingness to share your perspective here. The problem is that marketing/PR is a profession dedicated to finding whatever just-barely-technically-true weasel wording is required to make what they're getting paid for sound at least "ok" and preferrably "great!"

If you have time (definitely not expected) I would like to hear more specifics regarding this aspect of your statement:

> We don't do cross-domain tracking, or aggregate behavioral information across customers

vs. https://heapanalytics.com/terms

> We may also use data in an aggregated form for our own purposes

Re:Firefox 57 delays requests to tracking domains by codezero on Wednesday December 20, 2017 @01:50PM (#15972537)
Yeah, very good point, we should clarify what we mean by "for our own purposes."

What that means right now is that we use this data to improve query performance, and for internal monitoring. We do not use that data for commercial purposes, outside of the fact that we are ourselves a business.

Re:Firefox 57 delays requests to tracking domains by tedmiston on Wednesday December 20, 2017 @12:37AM (#15967283)
I also work for an analytics company too, or more accurately a data router that integrates with other analytics companies, including yours. I'd be interested in seeing your benchmark results as it's unclear to me whether / how this potentially impacts us.
Re:Firefox 57 delays requests to tracking domains by austincheney on Wednesday December 20, 2017 @09:19AM (#15969661)
> I can think of tons of ways to work around this if I thought it was a real issue, I don't. People who want to block analytics, trackers, ad networks, etc... know how, and this doesn't feel like it is targeted at those people, or even squarely at the tracking pixels.

A slow and shitty experience using the web shouldn't be the accepted baseline.

People who know how to block spyware can't block everything. There is a lot that causes the page to hang if not blocked in a certain way, provided that certain way is available via some kind of tooling.

Re:Firefox 57 delays requests to tracking domains by Sophistifunk on Tuesday December 19, 2017 @06:06PM (#15965305)
It's a grey area. But I am interested, do your ToS forbid your customers from on-sharing the data with cross-site aggregators?
Re:Firefox 57 delays requests to tracking domains by anfedorov on Tuesday December 19, 2017 @09:13PM (#15966457)
"on-sharing the data with cross-site aggregators"?

The ToS and Privacy Policy of an analytics company discloses what the that company may do with their client's users' data, not what the client can do with their own users' data.

There's another Privacy Policy between the client and the user where the client discloses what they may and may not do with user data and the user decides whether to become / remain a user.

There are also laws which dictate the data handling further on behalf of large groups of users, e.g. GDRP for EU citizens and, on this side of the pond, interesting Supreme Court cases being decided about what kind of data users could have property rights to: https://en.wikipedia.org/wiki/Carpenter_v._United_States

Re:Firefox 57 delays requests to tracking domains by codezero on Wednesday December 20, 2017 @12:37AM (#15967284)
Nope – not explicitly, that would be something within _their_ terms of service since it's their data. Their own customers would have to hold them accountable.

I know that's a cop-out – but I can't imagine a system where we could enforce some kind of downstream compliance.

Things like GDPR are a good way to make companies accountable and I look forward to that becoming more broadly accepted.

Re:Firefox 57 delays requests to tracking domains by jtmcmc on Tuesday December 19, 2017 @06:21PM (#15965434)
I am not the OP but from looking at their profile - https://heapanalytics.com/terms you can check there
Re:Firefox 57 delays requests to tracking domains by Yizahi on Wednesday December 20, 2017 @02:59AM (#15967837)
> wipe out data per-request

Why would you do that? You are providing a service to the people that is a pure benefit for them and doesn't harm them at all. Why would anyone want to delete such helpful data?

Re:Firefox 57 delays requests to tracking domains by erk__ on Wednesday December 20, 2017 @03:11AM (#15967887)
If they don't want a € 10 million fine they have to comply with GDPR, even if no one is going to use it.
Re:Firefox 57 delays requests to tracking domains by kabes on Wednesday December 20, 2017 @05:58AM (#15968615)
AFAIK, GDPR doesn't tell you there need to be an automated way to delete the data. If people can send you a mail with the request and you manually delete it, that's also fine. So if no one will use it, you basically don't have to do anything and be compliant (to this specific GDPR rule).
Re:Firefox 57 delays requests to tracking domains by PeterisP on Wednesday December 20, 2017 @07:43AM (#15969044)
Sure, but if people use your service and some 0.01% of them might send a request just as a matter of principle once GDPR kicks in, then it's quite plausible that the cost efficient way to handle this is to have an automated solution rather than a manual process that doesn't scale.
Re:Firefox 57 delays requests to tracking domains by whostolemyhat on Wednesday December 20, 2017 @07:45AM (#15969055)
From what I understand, as long as you can say there's a process in place (and could actually follow it) then you're compliant with the GDPR.