ip-blindness VS metadata

More here: https://github.com/bslassey/ip-blindness

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

> 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?

"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...

> 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)

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!

Which list is blocking archive.org? If "NextDNS Ads & Trackers Blocklist", probably some kind of mistake, write about it - https://github.com/nextdns/metadata/issues

You can find the NextDNS lists here: https://github.com/nextdns/metadata

You can always look at github. This is just the activity for their metadata repo: https://github.com/nextdns/metadata/commits/masterFeel free to check their other repos.

NextDNS gives you a whole bunch of 3rd party filters, maintained by random dudes in Github repos as a hobby. We support some of them too in the "3rd party filters" tab, however we don't encourage anyone to actually use them, as we have our own Native filters, that we've built up over the course of 5 years based on feedback for millions of Windscribe (our sister company) users. Our native filters are highly effective, and prone to much fewer false positives. We recommend you try them, you will be pleasantly surprised with how they perform. I guarantee you that you will spend 90% less time making whitelist rules for false blocks... or your money back :) "Native tracking protection" filters are all part of the IoT Filter. NextDNS has the individual toggles, which enforce this small set of rules. Out IoT filter enforces all of them, as well as 10x more things.

Here is the list: https://github.com/nextdns/metadata/blob/master/parentalcontrol/categories/video-streaming.json

Here's those native blocking lists from NextDNS: https://github.com/nextdns/metadata/tree/master/privacy/native

From https://github.com/nextdns/metadata/blob/master/privacy/blocklists/energized-ultimate.json the link used is https://block.energized.pro/ultimate/formats/domains.txt which currently contains nothing but comments.