3 ms·
I hope they do User-Agent next.
by sneak 6y ago
I hope they do User-Agent next.
- jefftk 6y agoThey've indicated they may: https://github.com/mozilla/standards-positions/issues/202#issuecomment-558294095 https://github.com/mozilla/standards-positions/issues/202#is... Commenting in support of Chrome's proposal to freeze the user agent and provide UACH instead.
- sneak 6y agoUACH is worse than a header. The server shouldn't get information about the client. Unsurprisingly, UACH is spearheaded by an ad tracking company that benefits from a moat caused by minimally viable/workable browsers costing millions of dollars and dozens of developers to implement.
- SquareWheel 6y ago> UACH is worse than a header. It's not. The header gives up all information by default. UA-CH works by request-only, and allows the browser to determine how much to send. This is easily controlled via native settings or browser extensions. The API also requires a secure connection, and specifically forces the server to admit to any fingerprinting (or legitimate use-case of data otherwise).
- oneeyedpigeon 6y agoAt least that might stop Twitter refusing to serve User-Agents it doesn't recognise.
- sneak 6y agoHow long until we see a CFAA prosecution based solely on providing a UA in the request that you're not "supposed" to use?
- floatboth 6y agoThere was a brief period of time last year when Twitch streams broke for me, turns out because my UA includes "FreeBSD" instead of an OS they know about. Eventually this was fixed.
- omoikane 6y agoCoincidentally, Mozilla's site is one that consistently blocks my user-agent (Lynx).