3 ms·
Yes I thought about it that's why "unless the user turns it off" comment in parens. I think out of 100 sites I visit everyday no website needs to access the aud
by superasn 7y ago
Yes I thought about it that's why "unless the user turns it off" comment in parens. I think out of 100 sites I visit everyday no website needs to access the audio api without my consent maybe except one or two which i can whitelist. Same for user agent, I don't think it should break if the container says I'm running firefox v65 or v67, etc.
- saagarjha 7y agoChanging the resolution sounds like it would break a lot of websites, though.
- shawnz 7y agoIf websites had to ask permission to enable responsive features like screen size detection, then nobody would use them
- dmitrygr 7y agoGood! Then maybe they'll go back to writing normal html and let my user agent present it to me how I like and how my device best does
- shawnz 7y agoIf that's how you feel, why not disable CSS?
- progval 7y agoIt was already possible to write CSS that adapts to various screen sizes before CSS became a privacy issue (ie. before CSS 3); except it was called regular CSS, not responsive. My guess is the difference between "regular CSS that adapts to screen size" and "responsive CSS" is that the former only has a single set of rules while the latter has different CSS rules that get enabled/disabled based on screen size. Conditional rules -> different content gets loaded -> server gets notified of what rules are enabled -> fingerprinting
- patrick5415 7y agoAgree. I wish the entire internet looked like GNU documentation page.
- NikolaNovak 7y agoAWESOME. Things went downhill once we started writing HTML which required knowing screen size ;-<