Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 57 delays requests to tracking domains

janbambas.cz

Post reply on HN
Print view View original

71–80 of 266 posts

Re: Firefox 57 delays requests to tracking domains

#71

Post by nyolfen »

thephyber wrote: post #41
flukus wrote: post #25

Earlier quoted context omitted.

Trouble is the amount of popular websites that simply don't care how long the page takes to load, 30 seconds would be acceptable to many as long as they get their advertising dollars. Users won't know who to blame. They might blame the site but they're just as likely to blame Firefox, Microsoft, their ISP or a virus. There needs to be a display saying "hey, this site is slow because it's tracking you in 15 different…

You're not thinking about this from a game theory perspective. Slow down pages -> more users bounce -> fewer ad impressions -> less ad revenue.

how is this game theory?

Re: Firefox 57 delays requests to tracking domains

#72

Post by sometimes42 »

marten-de-vries wrote: post #2

Interesting approach. I hope more browser vendors will adopt it. It comes with an additional advantage: if a website still needs to function when tracking domains are delayed a second or so, they likely will function too with said domain completely disabled (e.g. using extensions). Sounds like a win from a user perspective.

It seems short-sighted to me.

It's penalizing vendors who went through the trouble to make their scripts load asynchronously - which is done specifically to help page load performance. The worst offenders, who block the page with sync scripts, actually gain a competitive advantage from this change.

Re: Firefox 57 delays requests to tracking domains

#73

Post by betenoire »

qwerty456127 wrote: post #47

Isn't it anti-net-neutrality? Is it ok to build it into a major browser? I actually block all the tracking, malware, ads, social networks, fraud, gambling, porn (except a couple of porn sites I like :-)) etc domains I could find information about but this is my personal conscious choice, I have manually installed extensions for this and built the lists. Shouldn't other people do the same themselves too if they choose…

> Shouldn't other people do the same themselves too if they choose to or leave everything as is if they don't actually feel they need to change anything?

Your browser is no longer imposed on you, so switching to Firefox IS doing that thing yourself.

Re: Firefox 57 delays requests to tracking domains

#74

Post by Sophistifunk »

codezero wrote: post #68

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…

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

#75

Post by vim_wannabe »

kevin_thibedeau wrote: post #70

> Google’s A/B testing initially hides the whole web page with opacity: 0 Sounds like a violation of Google's own policies.

Now try Google's sweetheart project https://www.ampproject.org/ or any amp-powered site. They contain this gem of a boilerplate hiding page content for 8 seconds or until whatever script is finally loaded that overrides it:

    body {
      animation: -amp-start 8s steps(1,end) 0s 1 normal both; 
    }
    @keyframes -amp-start {
      from { visibility: hidden; }
      to { visibility: visible; }
    }

Re: Firefox 57 delays requests to tracking domains

#76

Post by legohead »

testvox wrote: post #36
legohead wrote: post #30

Earlier quoted context omitted.

This shouldn't be up to the browser. He even notes edge cases where this performs unexpectedly -- unacceptable. If this is such an issue and can actually be a performance increase, then someone should release a script with the same functionality. Or optionally make it an opt-in option in settings.

It shouldn't be up to the browser to implement web standards? What should browsers be doing then?

What is the web standard about delaying scripts deliberately encoded into the page?

Why downvote and no explanation? I want to know if I missed something.

Re: Firefox 57 delays requests to tracking domains

#77

Post by ucaetano »

qwerty456127 wrote: post #47

Isn't it anti-net-neutrality? Is it ok to build it into a major browser? I actually block all the tracking, malware, ads, social networks, fraud, gambling, porn (except a couple of porn sites I like :-)) etc domains I could find information about but this is my personal conscious choice, I have manually installed extensions for this and built the lists. Shouldn't other people do the same themselves too if they choose…

That was my thought: should browsers be content gatekeepers?

(Honest question, this is a very tricky area)

If Comcast decides to "block" 3rd party tracking and analytics content, would it be ok?

Re: Firefox 57 delays requests to tracking domains

#78

Post by jtmcmc »

Sophistifunk wrote: post #74
codezero wrote: post #68

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…

It's a grey area. But I am interested, do your ToS forbid your customers from on-sharing the data with cross-site aggregators?

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

#79

Post by dsr_ »

codezero wrote: post #68

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…

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

#80

Post by brokensegue »

ucaetano wrote: post #77
qwerty456127 wrote: post #47

Isn't it anti-net-neutrality? Is it ok to build it into a major browser? I actually block all the tracking, malware, ads, social networks, fraud, gambling, porn (except a couple of porn sites I like :-)) etc domains I could find information about but this is my personal conscious choice, I have manually installed extensions for this and built the lists. Shouldn't other people do the same themselves too if they choose…

That was my thought: should browsers be content gatekeepers? (Honest question, this is a very tricky area) If Comcast decides to "block" 3rd party tracking and analytics content, would it be ok?

network neutrality refers to network providers being neutral to the data they transmit. applications running over the network can do as they please.

by this argument ad-blockers violate net-neutrality.

Post reply on HN