TingPing

The malicious use is tracking. It can track who you know, where you live, what you own.

But it could… it’s arbitrary code execution and should be scary.

Of course there is bloat, but like high resolution assets alone of course are some MB.

I think what you are discussing is the move to only supporting declarative block lists. Long ago in Safari, and until very recently in Chrome, you could have JavaScript run to check and modify/block requests. The modern block lists still function the same (preventing a Request from ever being sent) just without dynamic code in the loop.

There is some fundamental misunderstanding here because content blockers can block requests by url.

The homepage says “off by default”

The main thing difference was WebExtension support. Upstream WebKit on Linux didn’t support them. However it will very soon.

ECH replaced what was called ESNI. Just was an evolving standard but it’s widely supported at this point, just rarely used.

Not OP but I don’t think DoQ is very interesting. DoH is nice because it blends in with HTTPS. Both do the protocol level things to avoid connection handshakes. The HTTP overhead isn’t that much really.

DoT is more complex than you’d imagine because it has to try hard to implement its own solutions to avoid handshakes.

Standard webkit content blocking, so it will filter requests and hide elements.

Depends on how much they care. They can take down repos containing any keys, or use heuristics to block clients.

Local llms aren’t super exciting unfortunately.

You can trivially configure it to forward logs to another service to manage them.

If a problematic bot is on any mainstream VPS it will just get shut down.

Networking is very core to webkit of course. But it has apis to block and modify requests.