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