Take it you didn't click "learn more"?
To sign into YouTube, you need to sign into Google.Com. that's the cross site script. Nothing scary, or unexpected.
Take it you didn't click "learn more"?
To sign into YouTube, you need to sign into Google.Com. that's the cross site script. Nothing scary, or unexpected.
Don't log into their services.
Don't visit the websites.
Don't even use HTTP, only Gopher and BBS.
Don't even use a computer, talk to your friends in person.
Don't even have friends, talk to the voices in your head.
Dont even talk with the voices in your head, destroy the illusory separation between self and other
Don't even talk to the voices in your head, your wife will think you're cheating on her.
The voices in your head are selling your data too.
Bingo! This is the way. I only open chrome when I need to log into a google/ alphabet site on the unlikely occasion. And close it immediately after.
Exactly if it can be used without logging in you don't have to log into everything.
If you access Google sites only in a special Firefox container, that still isolates your Google cookies from the rest of your tabs? Or does it just add a “you don’t get this from me” flag when it gives Google your user cookie, so it can pretend to not recognise you as it adds your web-browsing history to your ad-targeting profile (flagged appropriately as to keep it deniable, of course)?
Yes.
I have a google container for one account.
If I open a google site in another container it will be as if the account didn't exist.
The containers are all partitioned.
You can also partition off the cookie/storage per site by proxy used (in about:config).
So, you could create a container for google account 1 using proxy 1 and another container for google account 2 using proxy 2 and they will never have access to the data stored by either.
Out of curiosity, do you know if these containers also obfuscate browser and device fingerprinting? Separating cookies is important but unless it also blocks fingerprinters (in a different way for each container) the site will instantly know the same person is using both accounts.
FF doesn't really enable full fingerprint resistance by default. But it can.
These settings are some of what I usually use. All fingerprint values (that are able to be are randomised on every reload of a page.
Set secutity setting to custom, select known AND suspected fingerprinting > select from dropdown 'In ALL tabs'
Also: Because it's of no value / use to me, and (IMHO) a giant gaping privacy and security issue, I also disable webgl and webrtc, and navigator completely in about:config
Set the following:
WebGL webgl.disabled true
WebGL2 webgl.enable-webgl2 false
WebRTC media.peerconnection.enabled false
Navigator media.navigator.enabled false
RFP privacy.resistFingerprinting true
RFP options like bounce protection etc can also be enabled in config.
Check fingerprints on browserleaks.com, coveryourtracks.EFF.org, etc
Should be 100% unique fingerprint every time.
I think the "rest of your tabs" would have to be sites that already include google js (e.g. for "sign in with google" type stuff) to even know you have a google cookie (otherwise what's the point of FPI/ETP/TCP/network partitioning/no-3rd-party-cookies/etc.), but I could be wrong.
Is it sufficient to set the Enhanced Tracking Protection to "Strict" (which claims to block cross-site cookies in all windows), or is there something else you have to do?
So google is a privacy nightmare. Google pays firefox. There’s not a lot more dots to connect here. How is anyone surprised at things like this?
I don't know why you're getting downvotes.
All of the incentives line up. That's why you always examine incentives.
all 38 comments