ip-blindness
Our great sponsors
ads-privacy | ip-blindness | |
---|---|---|
16 | 7 | |
296 | 115 | |
1.4% | - | |
6.4 | 0.7 | |
about 1 month ago | about 1 year ago | |
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ads-privacy
-
If anything I've learned in marketing is that nobody knows anything except the algorithm - Another Performance Max post
Floc (not yet implemented): https://github.com/google/ads-privacy/blob/master/proposals/FLoC/FLOC-Whitepaper-Google.pdf
-
Firefox now blocks cross-site tracking by default in private browsing
Yeah, didn't word that right. They already do, but the flow of info will be reversed more or less. 3rd party data was where the money was made (still is but that's changing, which is what I'm getting at in general). Now sites generating first party data (which is less extensive - doesn't track your uid with PII across the web [generally speaking]) will be able to sell that data at a premium as 3rd party cookies die but 1st party cookies remain. and this all gets back to the FLoC api.
-
What will Happen to Google Display Ads in 2022?
Main solution for display remarketing will be the Federated Learning of Cohorts, the whitepaper is quite interesting
-
What is going on with "birds" names for the new generation of ad targeting technologies?
Why do Google's FLoC, TURTLEDOVE, Dovekey, Criteo's SPARROW, Magnite's PARRROT, NextRoll's TERN and Microsoft's PARAKEET all have similar bird-related names? This feels very cruel considering that in most cultures birds often symbolise freedom.
-
Google plans to stop targeting ads based on your browsing history
It's hard to fathom that statement coming from Google, a company that's built an empire by monetizing your browsing data. Looking forward, Temkin says the search giant is planning to use privacy-preserving APIs, like the "Federated Learning of Cohorts API" (FloC), to deliver relevant ads. That solution will rely on groups of users with similar interests, rather than drilling down to your specific behavior.
-
Google to stop selling ads based on your browsing history and drop cookies support for Chrome citing privacy concerns
They're aiming to implement what they called FLoC (Federated Learning of Cohorts) as a solution to avoid the need of third party cookies for ad trackers.Here's the whitepaper.
-
Google's article yesterday on new privacy practices. What exactly are the implications for Adwords?
That's going away, they will (supposedly) no longer have a profile that says TTFV is a golf lover or scotch drinker. But they will be put into a cohort and be targeted that way instead. I, admittedly, don't quite understand how this works, although the white paper seems like it could be helpful.
-
Google to Stop Selling Targeted Ads Based on Browsing History
"Instead, our web products will be powered by privacy-preserving APIs which prevent individual tracking while still delivering results for advertisers and publishers."
- The Federated Learning of Cohorts (FLoC) API is a privacy preserving mechanism proposed within the Chrome Privacy Sandbox. The goal of the FLoC API is to preserve interest based advertising, but to do so in a privacy-preserving manner.
ip-blindness
-
Intelligent Tracking Prevention is getting even stronger by also hiding the user’s IP address from trackers on IOS 15
More here: https://github.com/bslassey/ip-blindness
-
3rd party tags - Chrome
Yes, but have in mind that in a future it may not be possible. Take a look to the Gnatcatcher proposal: https://github.com/bslassey/ip-blindness
-
I Work on Ads at Google
> at the very least, the ad network will be able to see your IP and know that you like athletic shoes and visited www.wereallylikeshoes.com. If you visit some other domain first-ad-network.com owns with the same IP it within a small window of time, it can be pretty confident it's the same person and even store some client side data at that point. It feels like they can construct a reasonably good profile about their users by using that technique.
Yes, there are a lot of user identifying bits in an IP address. Chrome has two proposals: https://github.com/bslassey/ip-blindness I'm not sure what other browsers are thinking?
> That's considering the browser doesn't leak out any other potentially identifying information.
Which they definitely do. All the browsers are working on figuring out how to thwart fingerprinting, and it's really hard. I am glad, at least, that we were able to get Google Ads to publicly commit to not fingerprinting.
> when you click on the ad, they know one interest about you and, if you clicked in ads from other campaigns they run, they may reconstruct your profile well
Yes, when people click on ads in Turtledove the advertiser does learn something. This is a huge improvement to the status quo where advertisers learn things just by bidding, or an intermediate stage where advertisers learn things when they win an auction -- users don't click on ads very often, so the amount of information leaked this way is very low.
Exactly how much information the advertiser is able to learn on a click is still very much up in the air, so if you have views on this you might consider participating on the repo?
-
AdGuard publishes a list of 6K+ trackers abusing the CNAME cloaking technique
"Near-path NAT"[1] has been suggested as a mechanism that browsers can use to proxy requests through an intermediate server, similar to what you suggest.
[1] https://github.com/bslassey/ip-blindness/blob/master/near_pa...
-
Google to stop selling ads based on your specific web browsing
> and you know my IP address
https://www.chromium.org/Home/chromium-privacy/privacy-sandb... links to https://github.com/bslassey/ip-blindness for how they intend to handle this.
(Disclosure: I work on ads at Google, speaking only for myself)
-
Google says it may have found a privacy-friendly substitute to cookies
If you want to prevent fingerprinting, you need to look at where the identifying bits are coming from. (ex: https://coveryourtracks.eff.org/) The IP address provides enough bits to uniquely identify many users, and when combined with just a few more bits, to identify almost anyone.
TOR is one solution here, which you could potentially also describe as "adding forced MitM to every connection". The proposals in https://github.com/bslassey/ip-blindness/blob/master/near_pa... and https://github.com/bslassey/ip-blindness/blob/master/willful... have different tradeoffs than TOR, with the "TOR is painfully slow" problem being a big one.
If you have better ideas, though, I would be very interested in reading them!
What are some alternatives?
floc - This proposal has been replaced by the Topics API.
FTL - The Pi-hole FTL engine
turtledove - TURTLEDOVE
privacy-preserving-ads - Privacy-Preserving Ads
vanced-website-v2 - Source Code of the Vanced Website
privacytools.io - 🛡🛠 You are being watched. Protect your privacy against global mass surveillance.
Firefox-UI-Fix - 🦊 I respect proton UI and aim to improve it.
cname-trackers - This repository contains a list of popular CNAME trackers
identity-gatekeeper
stealth - :rocket: Stealth - Secure, Peer-to-Peer, Private and Automateable Web Browser/Scraper/Proxy