- From: Karl Dubost <notifications@github.com>
- Date: Tue, 20 Jul 2021 16:45:08 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/640/883776252@github.com>
@miketaylr wrote: > We'll have to disagree on this point. So many Opera Mobile and Firefox Mobile (Firefox OS and Firefox for Android) compat issues in the early days were caused by mis-parsing the UA string, or assuming all mobile browsers would have similar looking UA strings to the popular ones for a given region. I think providing a better, more predictable API is worth solving for, both for users and developers. A couple of years ago (during the Firefox OS days), Dailymotion gave me a sample of HTTP user agent strings (it was around 400,000 *unique* UA strings and their frequency). It included every type of requests browsers and bots alike. They gave the list for access to the API, the CSS file and a static icon. This was a wonderful trove of data. Google has Web properties with high traffic. (be careful that a sample for a limited period of time during a day will sway the data to a specific region of the world.) Is Google doing statistical analysis on the current UA strings? Are there patterns or features in this statistical set that could be explored? My thoughts are along, What are the UA string structure features extracted from the mass of the data (machine learning?) instead of the desired structure of the spec? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/640#issuecomment-883776252
Received on Tuesday, 20 July 2021 23:45:20 UTC