4 ms·

The Accept-Language header predates Google by many years, see https://www.rfc-editor.org/rfc/rfc1945#appendix-D.2.4 https://www.rfc-editor.org/rfc/rfc1945#appen

• mindslight 2y ago
  I certainly did not mean to imply that every browser fingerprinting vulnerability is due to Google née Doubleclick. What did I say to make you think so? And from a technical perspective, Accept-language doesn't seem terribly hard to mitigate - exactly one language at a time, and UI that allows a user to easily change to another, as if it's part of the logical URL. It's all the javascript APIs, especially the graphics ones with their loads of weakly-defined behavior, that are especially pernicious.
  • tatersolid 2y ago
    Sorry, mis-click threading issue on mobile. I meant the reply to this thread: https://news.ycombinator.com/item?id=42480099 https://news.ycombinator.com/item?id=42480099 Do any of the mobile-friendly alternative HN front-ends support commenting without giving up your creds?
    • fragmede 2y ago
      On mobile, the one I use has a share button that lets you open the comment in a browser.
    • fragmede 2y ago
      On mobile, the one I use has a share button that lets you open the comment in a browser and not have to login to the apo, though you miss some customizations like notification on comment replies.