Well, . Looks like I can't rely on either Chrome or Firefox not to with websites.
I would really love to just stop using the web entirely and go back to Gopher.
Firefox 57 delays requests to tracking domains
11–20 of 266 posts
Re: Firefox 57 delays requests to tracking domains
#12While I like the idea, a potential problem comes to mind. A list of what domains are tracking domains will need to be maintained. The need to maintain that list will possibly move the cat-and-mouse game of ads vs ad-blockers to the tracking list as well. I could totally see Alphabet paying Mozilla to remove analytics.google.com from the tracking domain list (because "it's just analytics; it doesn't track you or infri…
Google analytics tracks you and infringes on your privacy.
That's the reason I put that statement in quotes. A tag seemed like it set an unduly negative tone to the rest of the post.
Re: Firefox 57 delays requests to tracking domains
#13Well, . Looks like I can't rely on either Chrome or Firefox not to with websites. I would really love to just stop using the web entirely and go back to Gopher.
From the article:
> Scripts are delayed only when added dynamically or as async. Tracking images are always delayed. This is legal according all HTML specifications and it’s assumed that well built sites will not be affected regarding functionality.
(emphasis mine)
Re: Firefox 57 delays requests to tracking domains
#14While I like the idea, a potential problem comes to mind. A list of what domains are tracking domains will need to be maintained. The need to maintain that list will possibly move the cat-and-mouse game of ads vs ad-blockers to the tracking list as well. I could totally see Alphabet paying Mozilla to remove analytics.google.com from the tracking domain list (because "it's just analytics; it doesn't track you or infri…
> Scripts are delayed only when added dynamically or as async.
Re: Firefox 57 delays requests to tracking domains
#15While I like the idea, a potential problem comes to mind. A list of what domains are tracking domains will need to be maintained. The need to maintain that list will possibly move the cat-and-mouse game of ads vs ad-blockers to the tracking list as well. I could totally see Alphabet paying Mozilla to remove analytics.google.com from the tracking domain list (because "it's just analytics; it doesn't track you or infri…
> using data of the Tracking Protection database
This database is already being maintained and used for private browsing. I find it unlikely that an analytics CDN will play cat and mouse with Mozilla just so it's script will load a few milliseconds sooner.
Re: Firefox 57 delays requests to tracking domains
#16Well, . Looks like I can't rely on either Chrome or Firefox not to with websites. I would really love to just stop using the web entirely and go back to Gopher.
From the article: > Scripts are delayed only when added dynamically or as async. Tracking images are always delayed. This is legal according all HTML specifications and it’s assumed that well built sites will not be affected regarding functionality. (emphasis mine)
I don't know about you, but I don't browse the World Wide Implements-The-Specification-Perfectly Web.
Re: Firefox 57 delays requests to tracking domains
#17Earlier quoted context omitted.
From the article: > Scripts are delayed only when added dynamically or as async. Tracking images are always delayed. This is legal according all HTML specifications and it’s assumed that well built sites will not be affected regarding functionality. (emphasis mine)
I don't know about you, but I don't browse the World Wide Implements-The-Specification-Perfectly Web.
You should expect it, though.
Re: Firefox 57 delays requests to tracking domains
#18Interesting 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.
So the identified trackers' requests are.. merely delayed? Wowwie!
It's a great justification for building a database of perceived trackers though. Lots of useful info to slurp.
A better idea: DO NOT LOAD TRACKERS PERIOD.
EDIT: Look how the crowd treats alternative opinions. Can't have that, can we?
Re: Firefox 57 delays requests to tracking domains
#19Interesting 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.
So the identified trackers' requests are.. merely delayed? Wowwie! It's a great justification for building a database of perceived trackers though. Lots of useful info to slurp. A better idea: DO NOT LOAD TRACKERS PERIOD. EDIT: Look how the crowd treats alternative opinions. Can't have that, can we?
You write like an old grandma
Re: Firefox 57 delays requests to tracking domains
#20Is this net neutrality compliant ?
Net neutrality is in regards to the internet carrier, not the browser (or client). The browser is irrelevant to net neutrality.
I 100% agree with what you are saying, but in support of GP, I'm sure they were meaning the spirit of net neutrality (don't shape my request), NOT the legal definition of it.