News for hackers. Stuff that matters.
Re:EFF Browser Tracker Simulator by 1vuio0pswjnm7 on Wednesday June 16, 2021 @04:18AM (#27526149)
Well, I do not send the minimum as a privacy measure. I do it for speed and efficiency. Because I am so often using netcat, tcpclient or the like to make requests, I have learnt that most headers browsers send are totally unnecessary. I have had the opposite experience to what you describe. The web is really fast. Cloudflare especially. They offer ESNI, which I do use for privacy. No point in encrypting DNS if we ignore SNI. I make all requests to Cloudflare using an ESNI-enabled openssl as a backend for the forward proxy. Very rare to encounter the CAPTCHA. I am more annoyed by AWS who require SNI but offer no ESNI service.

Honestly, to me the web feels unusable if I try to use a "modern" graphical browser with Javascript and a DNS resolver enabled. The way most people use the web, I guess. To me it feels like a tar-pit. I do some basic stuff like banking, etc. that way, but for recreational use, I do not use the major browsers.

Re:EFF Browser Tracker Simulator by beermonster on Wednesday June 16, 2021 @06:44AM (#27526978)
The problem I descibe is that barriers get in the way the more you try and protect your privacy or security. It's not a speed issue - the web works very fast with me using NoScript and uBlock Origin. It's just lots of sites now longer like you visting or treat you as an attacker - you're soft blocked. If you ramp it up, even more of the web becomes a pain to use: e.g. using privoxy/polipo/squid, pi-holes, vpns etc, removing or changing headers, screen sizes and geolocation, timezone etc etc to make you less fingerprintable. Of course all you're really doing now is making yourself stand out like a sore-thumb.

The web is even faster when I'm using telnet/openssl s_client -connect, but that's not the point is it or even a fair comparison? I just want to browse the web without being tracked and categorised/labelled. It seems that's too much to ask.

Regarding CDN/Caching:

Google made a change[1] to how caching works which also has some CDN impact.

Instead of saving a resource with its full URL only, they have added two more bits of data to the saved information. Chrome saves the top-level site and the current-frame site next to the full URL of the cached resource. The browser uses the information to determine whether it should serve resources from the cache or not.

[1] https://developers.google.com/web/updates/2020/10/http-cache...