News for hackers. Stuff that matters.
Re:YouTube change served lower-quality video to Firefox 43 f... by kobayashi on Sunday January 10, 2016 @11:22PM (#10878782)
Are you suggesting unique randomized strings for every user?
[deleted]
Re:YouTube change served lower-quality video to Firefox 43 f... by debaserab2 on Monday January 11, 2016 @12:17AM (#10878970)
I'm sorry, but I still find the user agent string to be incredibly useful despite it's many shortcomings.

Not so much for deciding what to serve to a request, but moreso to analyze your audience and figure out from a technical perspective what is feasible and what is not. For example, a recent decision I made was to decide whether or not to rewrite a portion of our application in a javascript framework that did not offer IE8 support. I was able to quickly validate what portion of my userbase I was affecting by looking at user agent strings.

Request headers are a fantastic way to capture this little bit of information. Using javascript feature checking depends on a javascript engine successfully loading and parsing whatever scripts I've provided to the client. Request headers are simple plaintext that don't fail in even the most bare bones of situations.

Re:YouTube change served lower-quality video to Firefox 43 f... by fkooman on Monday January 11, 2016 @04:46AM (#10879841)
https://en.wikipedia.org/wiki/Progressive_enhancement https://en.wikipedia.org/wiki/Fault_tolerance

No need to do browser detection. Just make your site work without JS as well :)

Re:YouTube change served lower-quality video to Firefox 43 f... by jerf on Monday January 11, 2016 @09:03AM (#10880769)
Ten years ago, that may have been valid advice, when "dynamic" mostly meant "server-generated". But if you're creating a website that is heavily JS-based, it does no good to serve 25% of your customers a perfectly-standards-compliant page telling them their JS won't work, so the site can't do its thing. You still need to know what client base you are supporting, no matter what.
Re:YouTube change served lower-quality video to Firefox 43 f... by jakeogh on Sunday January 10, 2016 @11:30PM (#10878816)
That would be better, but not per user, per session. Currently I have surf(suckless.org) just pick a common one when I launch a tab (via tabbed): https://github.com/jakeogh/rndagent
Re:YouTube change served lower-quality video to Firefox 43 f... by pdkl95 on Monday January 11, 2016 @12:29AM (#10879001)
per-HTTP request

Nothing ever guaranteed the user agent header would be consistent or present. Any re-use of a user-agent string adds bits of data that can be used for tracking.

Re:YouTube change served lower-quality video to Firefox 43 f... by nitrogen on Monday January 11, 2016 @12:43AM (#10879039)
While we're at it, we need some solution to tracking based on browser window size. I'm one of the few people I know who doesn't maximize everything, so I'm probably 100% uniquely trackable just by window size.
Re:YouTube change served lower-quality video to Firefox 43 f... by quesera on Monday January 11, 2016 @01:01AM (#10879106)
Window size detection is done with JavaScript. Block it.
Re:YouTube change served lower-quality video to Firefox 43 f... by JupiterMoon on Monday January 11, 2016 @02:54AM (#10879460)
It can apparently be done with CSS by a determined website.
Re:YouTube change served lower-quality video to Firefox 43 f... by jakeogh on Monday January 11, 2016 @02:38AM (#10879411)
Disable JS by default. I do, and it makes the web better. Surf/tabbed makes this easy to do per process.