Well, that's nice. But do they tell you how to turn it off?

Under options, browser privacy and security settings.

An overview/commentary on the changes in FF69

[theregister.co.uk...]

Mozilla says that FF 69 blocks third-party tracking cookies, fingerprinting, and cryptominers by default

[blog.mozilla.org...]

The options have been there for at least a decade of version numbers, but oddly enough, few folks ever turned them on.

For those who want to return to the wild days of full exposure, go to options, privacy/security, Custom, and UNCHECK everything in sight. That will return you to near 1999. :)

--- The options have been there for at least a decade ---

It is the scary combination of words "Options & Setting" and "Click Here(in purple color via CSS like u already clicked on it)" that scared most of the behinds---seses_seseses even trying to learn about them since near to 1999. But then again most aren't aware of HOSTS file either.....

Why did it take a "69" to get here is whole other story....

ok, ok....

Hello-

Why did it take a "69" to get here is whole other story....

May be a matter of legal issues. Proposing it as an option, not set by default, was to test possible legal consequences. Blocking cookies, or access to third part files, this is altering the content of a site without the authorization of the owner, and I am sure this is border line. With the rising of privacy concerns and evolution of regulations world wide, this is certainly something which can be done now, more safely, than in the past.

--- May be a matter of legal issues.---

Naaah, me thinks it is all in the number! Also cuts on my time reinstalling OS/FF every time one of my relatives catch a "virus". Now I could just blame it on what happens after the "69".

Blocking cookies, or access to third part files, this is altering the content of a site without the authorization of the owner,

There's the obverse to that as well: the "customer" did not agree to third party content in the first place. :)

Sadly, for most websites, it is third party for revenue (instead of doing direct sales/advertising) to it does hurt... yet the user also has rights and GDPR is the first salvo with teeth in that regard. Things will only get worse for webmasters who rely on third party income from here on out.

3rd party cookies, shot dead, film at 11:00.

News at Sunrise: "Big Tech Loses Cookies, Skims by Fingerprints. That Java is not Coffee."

There's always another way and the bureaucrats will always be in catch up mode ... some 10-20 years later.

Any word on how this impacts Google Analytics and Adsense?

I use Analytics data to sell ads (in addition to Adsense), so by blocking Analytics entirely my ads are worth less even though they actually get the same exposure. Worse, I'm not sure if Adsense is countering this, or if I'm suffering from a lower RPM.

I'm all for user's rights, but this is one in a long series of attacks against free websites that survive by selling ads. If it keeps up then there's going to be nothing left but Facebook (and their many subsidies), Amazon, and Google.

Assuming you've updated things, your Analytics uses 1st party cookies, so there will be no effect here.

[developers.google.com...]

@RhinoFish, I had not changed my Analytics code... didn't even know I was supposed to! LOL Thanks for the post, I've updated it now.

All of your external services (Google Ads, Microsoft Ads, Facebook Ads, Criteo Ads, Analytics, ShareASale, Rakuten, etc) should have been overhauled in the last 12 months to switch from 3rd party cookies to first party cookies.

Apple's Safari changed first, with ITP 1.0. Then Firefox, the Safari ITP 2.0, then Chrome (browser) update, then Safari ITP 2.1, then FireFox ETP, then blah, blah...

Browsers are trying to protect users, by avoiding fingerprinting techniques and 3rd party cookies.
When this happens, let's say you site is abcd1234.com, and a sale is made, and your receipt page tries to pull a 3rd party cookie, let's say it's an affiliate program and the cookie is shareasale.com... the browser itself will not allow abcd1234.com to read the shareasale.com cookie, that cookie is a 3rd party cookie. Party 1 = you. Party 2 = your visitor. Party 3 = ShareASale.com. So, when a visitor lands from ShareASale, their newest code will set an abcd1234.com (first party) cookie, so the receipt page is able to read it later.

Today, anything you use to track that still uses 3rd party cookies will have a very high breakage rate. The browsers are ditching 3rd party cookie use.

Just saying, upgrade all tracking scripts, especially if you know they're using 3rd party cookies.

:-)

Just updated to version 69.01 Must be a minor update since there weren't any notes about it.

Tiny steps, @aristotle ... all headed in a direction. Pick and choose, pick and choose. :)

At present things can still be turned on/off under options, or more completely controlled in about:config.

@aristotle, I have v. 69.0 and it's on the release notes:

Enhanced Tracking Protection (ETP) rolls out stronger privacy protections:

The default standard setting for this feature now blocks third-party tracking cookies and cryptominers.
The optional strict setting blocks fingerprinters as well as the items blocked in the standard setting.

[mozilla.org...]

Chrome is my default browser, though, so I only noticed it after seeing this thread. I hadn't changed Analytics or Adsense in the last 12 months (and don't remember any emails suggesting it) so I had a period there of just missing data.

csdude55 -- Yes the release notes for 69.0 were discussed earlier in this thread. I meant that there are no new release notes for 69.0.1

Hmm will that have a impact on Google :)

Probably not as much as it seems on the face of it.

You know the old story about backroom deals, right?

Wanna bet there's been some deals made?

Meanwhile, I don't play. Run NoScript for YEARS for my PERSONAL browsing, so all this "new" stuff is "old stuff" to me. Heck, I even run it on WW---and this is one of the GOOD GUY sites!

Even better is that WW works with all scripts killed! My respect and gratitude to WW for being that way!

.

An update to 69.0.2 is available.
5.0 MB download
No release notes

Done! No visible changes and the security section appears unchanged. Wonder what was done under the hood?

An update to 69.0.3 is available.
5.4 MB download
Apparently a minor update - no release notes

This seems to coincide with the recent updates for Win machines last Tuesday... linked somehow?