3 ms·
There’s like a billion side channels to determine how big the screen is unless you just want to entirely break basic css. Which is a pretty unreasonable way to
by dymk 8y ago
There’s like a billion side channels to determine how big the screen is unless you just want to entirely break basic css. Which is a pretty unreasonable way to address this problem.
- oftenwrong 8y agoI block CSS altogether on most sites with uMatrix, so I do not think it is that unreasonable.
- rocho 8y agoDoesn't that make most sites unusable?
- oftenwrong 8y agoSurprisingly, most sites are perfectly usable with CSS disabled. They end up looking a bit like "motherfucking website"[1], or what you see in a text-based web browser. [1] https://motherfuckingwebsite.com/ https://motherfuckingwebsite.com/
- blattimwind 8y agoDisabling both CSS and JS actually works around usability issues on a bunch of sites ¯\_(ツ)_/¯ It's like reader mode, except it works on more sites.
- def_true_false 8y agoWouldn't loading all external links right away (think background-image) solve this? How does the site exfiltrate the gathered information without javascript or tracking pixels? Edit: Having a bunch of html buttons/links, showing a different to agents based on their resolution and waiting to see which ones they follow would break this, unless everyone crawls a lot of stuff they don't need. Pretending to be one of a few common sizes is probably a better solution.