https://proxy.example.com/ZGQgaWY9L2Rldi91cmFuZG9tIGJzPTEgY291bnQ9NTIgfCBiYXNlNjQgCg==
However, the "end game" of adblocking is far worse - the entire page becomes this: <!doctype html>
<html lang=en>
<head>
<meta charset=utf-8>
<title>null</title>
</head>
<body>
<canvas>Run the WebAssembly blob to render the page</canvas>
<script src="load_webasm_blob.js"></script>
</body>
</html>
The entire page becomes an giant obfuscated WebAssembly blob that renders the page into the canvas tag. The technologies of the open web like HTML become legacy baggage; a "web page" is just a stub loader for what would effectively be a statically linked executable binary that uses the canvas tag as a generic framebuffer.In this "end game", URL based blocking is irrelevant; most page assets become part of the blob. The question "is this an ad/tracker/virus?" becomes undecidable; answering any question a page's behavior requires running potentially hostile code or solving the Halting Problem. Some people don't want an open web that respects things like user agency. They want control. They want the "web page" to be an opaque binary blob that nobody can investigate or modify. They want full control over what the user sees and is allowed to do. They want TV.
Of course, the publishers will need to trust the advertisers, but I don't see how they have much choice...
Personally I don't think the strength of p2p is only trust, it's delegation. If you have peer to peer encryption running, the possibilities are endless.
Add a statistical "proof of authenticity" and you have an unbeatable anti censorship mechanism that can also identify in-page modifications and weed out malicious MITMs in between.
I guess the only thing that’s necessary now is to set it up so that the node could be another mobile client. Maybe it’s possible with webrtc or an extension?
[1] https://github.com/bslassey/ip-blindness/blob/master/near_pa...
Even if it's encrypted, I feel like someone smarter than me would figure out how to do bad things with this.
> Under this scheme it would become impossible to trace who you are.
This is how i2p works, in a nutshell. Every i2p user is a node in the network for others to proxy through.
Unfortunately, hiding your IP and geographic location isn't enough to stop fingerprinting and other forms of de-anonymization.
I think Google pre-emptively locked down Chrome API to prevent ML based blocking from working. This would explain their fixed URL block list and removing interactive API
in the future, given sufficient CPU resources on the clients, another method could be browser page-rendering engines that use advanced machine learning image recognition to categorize and blank out ads, no matter where they come from.
edit: I almost wonder if this could be done safely in a decentralized manner. Everyone runs a BitTorrent like service and when you make a request the swarm proxies it to a specific node who then serves the page back to you.
Under this scheme it would become impossible to trace who you are.