[hn_throwaway_99]

Yeah, this take on "I also try to block first party tracking" is just weird in my opinion, or at least impossible (beyond just normal cookie blocking tools).

The ways most sites utilize AJAX and JS, there is just no consistent way to block "tracking calls" vs. blocking requests needed for particular pieces of functionality and data.

[matheusmoreira]

> there is just no consistent way to block "tracking calls" vs. blocking requests needed for particular pieces of functionality and data

At some point, browsers will gain firewalls and packet inspection and filtering capabilities.

We should be able to inspect the data sites are sending and receiving asynchronously via Javascript. We should be able to automatically delete or redact private information from JSON payloads. What if uBlock Origin could automatically anonymize unique identifiers that some Javascript code is trying to exfiltrate?

[abestic9]

I would expect to see ad/tracker blocking technology to advance as the users encounter more invasive types of tracking. But what if the server requires that information as part of a request to serve content in it's response?

This will always be a cat and mouse issue, and unfortunately right now most of the authority is on the server side. The data-driven web that TimBL envisions is just not profitable enough and content has to be heavily intertwined with distractions and trackers to monetise us cattle. See RSS.

[forgotmypw17]

Exactly, there is a lot of trust involved, even without executing JavaScript, but especially when so. This is why I stay away from sites I don't find trustworthy.

I also close the tab if I'm presented with a paywall, a modal newsletter subscription prompt, impossible cookie banners, etc.

I think of it as a "the medium is the message" type of thing, and if the medium is tainted then the message can't be any better, so why read it?